edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Will Marshall (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (EDGENT-415) Improve our message
Date Wed, 24 May 2017 21:26:04 GMT

    [ https://issues.apache.org/jira/browse/EDGENT-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023720#comment-16023720
] 

Will Marshall edited comment on EDGENT-415 at 5/24/17 9:25 PM:
---------------------------------------------------------------

Here's a single data point of how our message is coming across, I noticed this posting on
reddit:
https://www.reddit.com/r/IOT/comments/63a76w/edgent_programming_model_and_microkernel_style/?st=j33hu619&sh=7d845256

"small footprint" and "java" don't really go together.

" "Edgent enables you to shift from sending a continuous flow of trivial data to the server
to sending only essential and meaningful data as it occurs."

I don't know why this is touted as something new and exciting everywhere IoT is discussed
in relation to edge devices. This way of operating has been done since forever in M2M. You
also don't need a large Java application to do so - sensor networks using 8-bit processors
have done this for more than a decade."

This person seems to have latched onto the data reduction use case of Edgent without understanding
its place as a streaming framework.





was (Author: wcmarsha):
Here's a single data point of how our message is coming across, I noticed this posting on
reddit:
https://www.reddit.com/r/IOT/comments/63a76w/edgent_programming_model_and_microkernel_style/?st=j33hu619&sh=7d845256

"small footprint" and "java" don't really go together.

*"Edgent enables you to shift from sending a continuous flow of trivial data to the server
to sending only essential and meaningful data as it occurs."

I don't know why this is touted as something new and exciting everywhere IoT is discussed
in relation to edge devices. This way of operating has been done since forever in M2M. You
also don't need a large Java application to do so - sensor networks using 8-bit processors
have done this for more than a decade.*

This person seems to have latched onto the data reduction use case of Edgent without understanding
its place as a streaming framework.




> Improve our message
> -------------------
>
>                 Key: EDGENT-415
>                 URL: https://issues.apache.org/jira/browse/EDGENT-415
>             Project: Edgent
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Dale LaBossiere
>            Priority: Critical
>
> There's been more than one example of someone who after hearing and/or reading some about
Edgent says "I still don't know what Edgent is".
> We need to improve the messages on our Website landing page, doc website, and probably
Apache project page to more clearly get our message across.
> After further explanation of a sample, you can get:
>     "oh it's an SDK"
>     "oh... you're not running the topology, you're building it, then running it"
>     ... but still...
>     It's tied to Android?
>     It's tied to Watson IoT Platform?
>     It has an API for accessing sensors?
> Yeah, the the doc has content that addresses most of that.  It's apparently not as effective
as it needs to be.
> IMO, a phrase that we use in a few locations "Edgent is a programming model and micro-service
style runtime ..." seems to be the first place to start.  Perhaps something like this would
be better: _Edgent is an SDK for creating event driven stream processing style analytic applications
to embed in small footprint edge devices and IoT gateways.  Smarter Edgent-based devices and
gateways can do realtime analytics on continuous streams of data, ...._"  you get the idea.
> The website landing page also has wording that says Edgent (doesn't say an Edgent based
application) performs realtime analytics, makes devices more intelligent, Edgent can adjust
controls..., Edgent enables connected devices, etc.  Very misleading IMO.
> On the Documentation site landing page, it talks mostly (only?) in terms of reducing
data.  Nothing about how a smarter device (edge resident analytics) can make devices more
autonomous: reduce decision making / action latency and overall be more autonomous while disconnected
from the cloud.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message