Skip to main content

IoT and Edge in 2022: Looking Back & Looking Forward

At last, 2022 is with us. In my native Canada, the month of January usually brings polar temperatures — think -25 Celcius (-13 Fahrenheit) and below. When it is so cold outside, it is a good time to think about the past year and look forward to the year ahead. In that sense, January is the perfect name for the month. You see, the month of January is named for the Roman god Janus. Janus is the god of beginnings, time, and transitions in ancient Roman religion. He is represented as having two faces; he could see the past with one and the future with the other. In this post, I will consider both the past and future of the Eclipse IoT and Edge ecosystem.

2021 was great!

When I look behind, 2021 has been a banner year for us. Our celebration of the 10th Anniversary of the Eclipse IoT working group at EclipseCon has been a wonderful moment, and our community is stronger than ever. Moreover, the 2021 edition of the Eclipse IoT and Edge developer survey report has made quite an impact. Since the report launched on December 8, 2021, close to 2,500 IoT and Edge enthusiasts and professionals have downloaded it. All of this would not have been possible without our contributors and committers' hard work and dedication. Thank you, everyone!

2022 will be even better!

When I look to the year ahead, I see plenty of opportunities for our community. In my opinion, the three most exciting ones are Sparkplug, CORE-V, and Rust.

Through 2021, the committers to the Eclipse Sparkplug specification project have worked hard to improve the specification document. This was necessary to make it clearer, easier to understand, and simpler to implement. In 2022, the team will publish the first version of the Sparkplug specification under the Eclipse Foundation Specification Process. In parallel, the Foundation will launch the Sparkplug compatibility program. This will provide a robust foundation for the working group and technology to grow. Our survey showed that MQTT dominates the field of IoT protocols, with 44% of respondents stating they use it. However, the lack of interoperability in the MQTT ecosystem is still a concern. Sparkplug changes that, which is why it will see significant growth in 2022.

The only thing better than open-source software is open-source software running on open-source hardware. RISC-V has seen significant adoption recently. 8% of the respondents to our 2021 survey mentioned they use processors based on the ISA. Moreover, 6% said they leverage chips based on the open-source CORE-V designs developed by the OpenHW Group. I expect those numbers to be even better in 2022. IoT developers need stable, validated platforms to work with. CORE-V delivers that in droves, with flexibility that most proprietary designs simply cannot offer.

Finally, there’s Rust. C is still the number one programming language for constrained devices in our survey, with C++ also part of the top five. There are many reasons for that. C is fast and portable. It is the cornerstone of a whole ecosystem of tools, frameworks, and libraries. However, it leaves memory management to the developer, which results in more security issues. Rust emerged as a credible alternative to C since it provides error-proof memory management. In our community, Eclipse zenoh is written in Rust. Our friends at Red Hat have also built a constrained device and Cloud stack at the Drogue IoT project. I see those two projects collaborating in 2022, and I suspect other Rust-based projects will appear in the Eclipse IoT lineup.


Popular posts from this blog

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 

[Guest Post] Edge Computing and Open Source in Europe: A New Hope

This is a guest post by Alberto P. Martí, VP of Open Source Community Relations at OpenNebula . For everyone in the European cloud market with a passion for open source, these are exciting times. For years, tech journalists and market analysts have been predicting that edge computing was going to bring a paradigm shift to the cloud, and now we are starting to see the form that this disruption is going to take—at least in Europe. Technically speaking, there is little doubt that deploying applications and processing data at the edge comes with a number of benefits, and not only in terms of reducing latency and improving user experience. We are talking about expanding service availability to better deal with infrastructure incidents, reducing data transfers and the energy consumption and security risks associated with them, as well as minimizing vendor dependency by expanding the number of available providers. It comes as no surprise that the European Union has identified edge computing a

The Edge of Things: A Name That Means a Lot of Things

I have a fantastic job. When people ask what I do, I say I manage IoT and Edge Computing programs at the Eclipse Foundation. This is true yet is an oversimplification. What I actually do is a bit more complicated than that. I need to keep an eye on over fifty relevant Eclipse open-source projects. At the same time, I help animate three distinct communities: the Eclipse IoT , Edge Native , and Sparkplug working groups. All three have something to do with IoT and Edge Computing, each with a slightly different angle. And here is my problem: it is hard to convey all the nuances of everything our IoT and Edge community does in a single word. IoT, of course, includes Edge Computing. Deploying compute, storage, and networking resources as close to the source of the data as possible makes complete sense. However, Edge Computing is an architecture that applies to many other use cases, such as gaming or videoconferencing. None of those two concepts completely encloses the other. And no single w