Hi Julian,
welcome here on the Edgent list :-)
Well I can't speak for the rest of the team, but for me Edgent is currently
sort of the following:
- For me Edgent is the ideal entry point for any sort of IoT system
- I like to compare it with Kakfa-Connect, but without the cloud (ok we can
read and write to clouds, but Edgent is not a cloud based system)
Especially if you want to operate in constrained environments, such as:
- Limited processing power
- Low energy consumption
- Low memory consumption
- Narrow/Unreliable/High-Latency network connectivity
Then is where you can cross all the cloud based streaming frameworks off your
list.
Regarding Akka Streams ... well the presentations I did some time ago with my
little Rapiro Robot, were based on Akka Streams ... that was why I fell in love
with Edgent when I heard about it at ApacheCon NA in Miami. For me, Akka
Streams totally fries my neurons. It's far too complicated. And as soon as you
want to work with Fan-In/Fan-Out and Backpressure ... well ... I thought it was
nuts ... but I have to admit that I'm no Akka or Scala pro, so please don't
treat this assumption as a fact. It's just my opinion.
Does that answer your question? If not ... feel free to ask :)
Chris
Am 06.08.18, 13:50 schrieb "Julian Feinauer" <j.feina...@pragmaticminds.de>:
Hi all,
this is my first post on the Apache Edgent mailing list and first, let me
say, that I’m quite impressed by all that has been done with regards to IoT and
Edge Processing in this project.
As I observe the project for a long time now and we start to see many use
cases with our customers we decided to get deeper in touch with the community.
When reasoning about the architecture of a new system for our new costumers
including a lot of “IoT” communication we obviously came by apache edgent.
Can you say, what in your opinion the unique selling point of edgent is?
Is the focus on the interaction with Cloud Based IoT Services or do you see
the low footprint stream processing also as one advantage of edgent?
I tried to get a really good overview over the remote control capabilities
and the MXBean integration, but I think I’m not at it, yet.
We looked at different stream processing platforms like Flink, Spark (which
are everything except low footprint) but also Akka streams which seems to fit
very well with “low footprint”.
So do you see Akka streams as an alternative to Edgent when one only uses a
“Simple” Topology with a DirectProvider and no integration to Remote Services
or Control and Command Servers or anything?
I would love to hear your opinion on that!
Best
Julian
pragmatic minds GmbH
