>Internal Use Only License Grant. TIBCO hereby grants you a limited, non‐transferable, non‐exclusive license to use the software solely for your internal business purposes.<p>"open source"
12 hours off HN & your project gets posted! Phew :)<p>I'm the PM on Project Flogo and welcome your questions + feedback. As some have noted on the interweb, it's a pretty big step for an enterprise sw vendor like us, to open up a core piece of our technology, so your constructive feedback gets a lot of attention around here and shapes it!<p>Couple of quick clarifications:<p>- All the repos (CLI, Library, Contrib and Services) except the top-level repo are BSD-licensed. The top-level repo is docs+samples, so we have put it under a free-beer license. However, we are in principle open to putting it out under BSD or a CC license as well.<p>- At its core, Flogo is a process engine that executes flow definitions consisting of activities. These flows are triggered by events happening in the real world. Triggers could be HTTP, MQTT, CoAP, etc. & activities could be AWS IoT, Log, HTTP, Send MQTT, etc. There is a fairly simple SDK to build your own activity or trigger and bring those along.<p>- We are actively working on a Web UI to model the flows instead of handcrafting the json DSLs or writing code.<p>- The runtime footprint comparison is for apps with equivalent functionality (Think a flow like MQTT Trigger -> Log Message -> HTTP Request -> Send MQTT). We just chose 2 common frameworks to showcase the difference in runtime footprint. We love Node & Java - it's just that for Edge integration microservices we chose Golang - and the runtime footprint was a key decision factor among others.
It should be an IoT integration framework, which has 3,3 MB. That sound huge to me. If I have an embedded processor that has 1 MB of Flash, than that is already huge. Still this has to fit my application besides that framework.
Google Brillo and Weave are essentially providing the same functions for Google's evosystem for IoT which connects to Google Cloud Platform. How does Flogo compare with Brillo + Weave?
I have been doing "IoT" for 10 years and after checking the website and the github repo I still have no clue about what flogo does.<p>Isn't it like some basic http api for "triggers"? Is this what people think IoT is about?<p>More importantly, can these basic set ups make money for some?