Skip to main content

A Shared Vision For Edge Computing

The Eclipse Foundation is a member-driven, vendor-neutral organization. I cannot count the number of times I have said this since I started at the Foundation in February of 2019. As a Foundation staffer, my job is to serve the community and assist its members in driving their initiatives. During the past 12 months or so, I have had the privilege to work closely with our Edge Native Working Group on what I consider to be a very special initiative.

After its creation in December 2019, one of the main goals of the Edge Native Working Group has been to define its vision for Edge Computing and share it with the rest of the industry. The community decided at that time to write a comprehensive white paper to accomplish this goal. At first, I simply supported that effort, but ended up writing part of it.

Today marks the launch of our white paper, titled “From DevOps to EdgeOps: A Vision for Edge Computing”. And I am proud to say that my vision for Edge Computing is, in fact, a vision shared by the Edge Native Working Group.

So, what will you find in it? A comprehensive analysis of the market, a clear definition of what Edge Computing is and our vision for its future. Here is our argument:

  1. The challenges of Edge Computing are distinct from those of Cloud Computing. Using Cloud approaches, tools and platforms at the Edge without modifications to meet these edge challenges will simply not work.

  2. Industry experts differ on their opinions about whether there is a single “Edge” or many Edges. Our perspective is that there are so many edges that the space from the very end of the Edge and all the way to the Cloud can be seen as a continuum. This means that a proper edge platform will need to be able to position the various mix of devices and components at any physical location found in this continuum.

  3. Edge Computing is about bringing computing power and storage as physically close to the source of the data as possible. This means edge computing nodes have to face many constraints that are not typically found in the Cloud, such as limits to power consumption, unreliable networks and many others.

  4. DevOps tools and techniques transformed the way we build and deliver software. However, DevOps was born in the Cloud. Since Edge environments are radically different, there is a need to adopt a new paradigm -- DevOps for the Edge. This is EdgeOps: our vision for the present and future of Edge Computing.
What makes this white paper special is that it's been written by actual, experienced practitioners of Edge Computing. Working on it with the other authors has been a real pleasure. Many thanks to Robert Andres (Eurotech). Luca Cominardi (ADLINK Technology) and Kilton Hopkins (Edgeworx) for their dedication in bringing this white paper to light.

You can download the white paper here.

Comments

Popular posts from this blog

Eclipse ThreadX: Charting our course for 2025

On November 21, 2023, Microsoft announced that it was contributing Azure RTOS to the Eclipse Foundation, which gave birth to the Eclipse ThreadX project . Since then, the project team and Eclipse Foundation staff have been working tirelessly behind the scenes to transition ThreadX to a true community-driven open source project and ensure its continued certification for safety-critical applications. In this short post, I will review the major milestones of that first year and share what to expect from the team in 2025. ThreadX v6.4.1 On February 28, 2024, the ThreadX project released version 6.4.1 of ThreadX and its companion modules. This release, the first made under the Eclipse Foundation development process, completed the transition of ThreadX to open source. From a technical standpoint, there were no changes from the prior 6.4.0 release. And yet, v6.4.1 represents a significant milestone. The Eclipse Foundation intends to certify ThreadX v6.4.1 for safety-critical applications. Yo...

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 ...

2025 Embedded and IoT Developer Survey: 10th Time is the Charm

The 2025 edition of the Eclipse Embedded and IoT developer survey is now underway! Take the survey now – it only takes a few minutes. Your insights and opinions will help shape the future of Embedded and IoT systems. Let's make a difference together! Although our public archives only date back to 2019 , the Eclipse Foundation has been conducting this survey in one form or another since 2015. To my knowledge, it is the only one of its kind managed by an open source community. Your participation in this survey is not just a contribution, but a vital part of the open source community's growth. Moreover, all of our survey reports are made available under the CC BY 4.0 license , meaning that you can freely share and adapt them simply by giving appropriate credit. In other words, your participation in the survey benefits not just commercial interests, but the entire open source community. As usual, the survey will gather precious data on embedded microcontroller architectures, commu...