12 Thoughts on the Eclipse IoT Developer Survey

The Eclipse IoT foundation published results of IoT developer survey – this is the third annual installment. Eclipse IoT, under its umbrella, has several significant open-source IoT projects. And if you have not looked at it – it is definitely worth checking out and to be considered for your IoT development strategy.

I would strongly recommending reviewing the survey and also signing up for a virtual meetup that they are hosting to discuss these results. It has very good insights into the state of IoT from a developer perspective. I must admit that I kept intending to fill in the survey myself but despite several reminders ultimately never filled it!.

I would certainly be leveraging the trends in this survey in formulating my strategy with the following thoughts/observations:

1. Distributed Software: IoT applications are distributed across Sensor (Device / Thing etc.), Gateway (Edge/Fog/Hub) and Cloud. This year’s survey has the feedback split across the above three. And that’s the right way to look at it because each aspect requires different approach, perspective and strategy.
2. Stats 101: Note that the percentages do NOT add up to 100, keep that in mind as you look at the look at them. This is, probably, because it reflects reality – there is no single correct answer. This also, probably, points to a trend that there are multiple projects going on or multiple products being worked on by the same set of developers.
3. Javascript is #1 in Cloud: I came to a different conclusion than the survey. Javascript, NOT Java is the #1 language used for IoT for the Cloud. I expect that trend only to accelerate. The reason I claim that is that the survey results are split in Javascript AND Node.js. Node.js is a framework (for a lack of better word in the context of this article) – Javascript is the language. The only discrepancy I can think of is that Javascript may refer to pure User Interface or Web Interface development?  The numbers on Gateway are also split into JS and Node.js – and when you put them together – it is higher than C/Python/C++.  And by that token – Javascript is #2 as a choice of programming language on IoT Gateways.
4. Linux dominates: Raspbian and Ubuntu are winners. Canonical would be very happy or probably already knows this since they are ditching the smartphone/tablet focus and switching over to IoT. I am pleasantly surprised that it dominates constrained devices as well. Reading between the lines – the popularity of Raspberry Pi as a prototyping devices drives Raspbian?
5. IoT HW Architecture: The percentages do not represent device or gateway volumes. This is important to bear in mind especially when you look at the results for IoT Hardware architectures. For example 32.9% of developers use Intel x86_64 for Gateways – to state the obvious – these are not 32.9% of gateways but the number of developers.
6. Cloud Programming: Ruby On Rails is missing? No mention of RoR in the IoT Cloud. (May be the option did not exist in the survey).
7. Machine Learning (Slide #32): Interesting to note that 29.5% of developers claim that they are building machine learning.
8. Cloud Services for IoT: No IoT platform other than GE Predix made this – e.g. no PTC. (this is a blog post in itself given the huge number of IoT platforms out there).
9. Connectivity Protocols: This actually mixes both – transport or medium of connectivity and also the ‘data’ protocol. To give an example – Cellular, from a developer perspective, is IP (Internet Protocol). Same with Wifi & Ethernet yet TCP/IP is broken out separately. Zigbee & Thread are mapped to IEEE 802.15.4. This is important to keep in mind because you can’t easily split IoT into black and white categories. There is shades of grey all around.
10. Messaging Protocols – yet another sign – there is absolutely no point in trying to get to one standard – the use case should drive if you want to use HTTP, MQTT, XMPP, CoAP etc.
11. Industrial Protocols – this is a great slide. It would be interesting to dig into what “None” really implies – does it imply that it is proprietary?
12. Leading Indicators – these results are leading indicators – of things that are to come. The survey is what the developers are working on (presently or in recent past). And that makes them more interesting because they are indicators of where IoT is heading.

 

 

Advertisement