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.

Labels:

Comments

Post a Comment

Popular posts from this blog

[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
Post a Comment
Read more

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 
Post a Comment
Read more

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
Post a Comment
Read more