Skip to main content

Eclipse IoT: The Next Ten Years

If you attended EclipseCon 2021, you probably heard about the 10th anniversary of the Eclipse IoT Working Group. Throughout the end of 2021 and into 2022, we will celebrate this significant milestone together. 

Our first step to commemorate the occasion has been to organize a panel regrouping five early contributors to the working group: Benjamin Cabé, Marco Carrer, Andy Piper, Ian Skerrett, and Andy Stanford-Clark. During the conversation, they reminisced about the early days and shared their vision of the future. I acted as the panel's moderator, and I must say I have been impressed by the insights shared by our pioneers. 

I want to share what I think the next ten years will have in store for the Eclipse IoT working group in this blog post.

1. Edge Computing Will Be an Integral Part of IoT

Optimizing power consumption, reducing latency, keeping bandwidth usage under control... There are many reasons to leverage edge computing in IoT deployments. As 5G coverage grows and EdgeOps platforms mature, I expect that enterprise IoT deployments where devices are connected directly to the cloud will become increasingly rare. In addition, orchestration platforms and protocols built from the ground up for the edge, such as Eclipse ioFog and Eclipse zenoh, will see their adoption grow.

2. Open Source Hardware Will Dominate

Nowadays, most software is updated several times per year. IoT solutions, on the other hand, rely on hardware devices deployed in the physical world. They are often in hard-to-reach places and, consequently, costly to replace even if the devices themselves are affordable. Therefore, organizations expect them to last a long time. Moreover, in the context of industrial automation, most machines now ship with built-in sensors and connectivity, but their lifecycle will still be in decades. Open-source hardware will help ensure the availability of critical hardware components over the long term.

3. Open Source Specifications Will Drive Standardization

Traditional standardization organizations, such as the ISO and the IEEE, are here to stay. However, there is a need for processes such as the Eclipse Foundation Specification Process that mandate work in the open and maintain a level playing field between stakeholders. Another advantage of the EFSP is that it accelerates innovation by relying on a self-certification model for compatible implementations of the specification, which significantly reduces the time-to-market of compatible products.

And there you have it! Whether my predictions will be accurate or not, one thing I'm sure of is that the second decade of Eclipse IoT will be even more exciting.


Popular posts from this blog

Eclipse Amlen v1.0: A Milestone in the Growth of MQTT

Over ten years ago, the Eclipse Foundation launched the Eclipse IoT working group . MQTT was one of the pillars of that launch. The first three projects were Eclipse Paho , a collection of MQTT clients, Eclipse Mosquitto , an MQTT broker, and Eclipse Kura , a Java/OSGi solution for IoT gateways that supports the protocol. To say that MQTT is in our genes would be an understatement. Since then, usage of MQTT has grown significantly. Year after year, the simple yet powerful publish/subscribe protocol is the most widely used IoT-specific protocol in our annual developer surveys . For example, in the 2021 edition, 44% of respondents stated they are using it. We like to think we are at least partly responsible for that. By the way, our 2022 survey is currently underway; you have until June 15, 2022, to participate. Click here to share your insights after finishing this post, of course. IBM has been a key player in our MQTT ecosystem for a long time. In 2021, the company brought its commit

Eclipse IDE for Embedded Developers Now Runs on the Raspberry Pi!

The Eclipse IDE is the project that started it all for the Eclipse Foundation . From the beginning, Eclipse IDE was meant to run on multiple platforms; it now supports Linux, Mac OS and Microsoft Windows. Since it is written in Java, it also supports multiple processor architectures. However, support for 32-bit architectures has been dropped in version 2018-12. This meant recent versions of the IDE would not run on the Raspberry Pi anymore. The introduction of the Raspberry Pi 4 in June 2019 gave hope to Eclipse on Pi fans. With its 64-bit quad core ARM Cortex-A72, the Pi 4 was a good hardware platform to work with. It became even more attractive in May 2020, with the introduction of the 8Gb variant. The Eclipse community took notice of those developments. Version 2020-09 of Eclipse IDE now ships with experimental support for 64-bit ARM (aarch64) on Linux.  Those developments mean embedded and IoT developers can now work on the Raspberry Pi 4 by installing the plugins provided by the 

Sparkplug: From Specification to Standard

This week, the Eclipse Foundation announced that the Sparkpug® 3.0 specification has been published as an International Standard. That sounds impressive. But what does it mean, exactly? And how will this impact the evolution of Sparkplug? To answer this question, let’s take a step back and consider what standards are. The technology industry loves standards. For example, USB is a set of standards managed by the USB Implementers Forum, Inc. (USB-IF), a non-profit corporation founded by the companies that developed the USB specification. The Eclipse Foundation describes Jakarta EE as a standard: a set of  specifications for enterprise Java application development. In the IoT and Industrial Automation world, OASIS Open also presents the MQTT protocol as a standard. However, standards play a much more pervasive role in society. There are standards for building homes and others that define how cars should work. Standards permeate our lives. To understand the significance of this week