EdgeOps Fundamentals: A View of the Ecosystem
Last time, I discussed the challenges that Edge Computing can help you overcome. Given how versatile and flexible edge computing is, the ecosystem of open-source projects you can tap into to implement solutions is extensive. This post will provide you with a high-level overview of this ecosystem.
The EdgeOps Matrix
One of the most interesting features of our white paper on EdgeOps is the EdgeOps Matrix. As you can see below, this matrix aims to position popular Eclipse and non-Eclipse open-source projects on the edge-to-cloud and development-to-operations continuums.
Naturally, many of the projects showcased in the matrix can be used in a range of locations along the edge-to-cloud continuum. For example, lightweight Kubernetes distributions such as K3s and MicroK8s are suitable for deployment even on constrained edge nodes alongside IoT and Edge devices. And, of course, protocols such as Eclipse zenoh are embedded into applications by developers but involve infrastructure components (the zenoh router) managed from an operations perspective. Consequently, pinpointing projects at specific coordinates in the matrix is an oversimplification. However, trying to represent the full range of possibilities in a static image would have been pointless since the resulting image would have been a visual mess of overlapping shapes.
Another important remark about the matrix is that Eclipse Foundation project logos are in color, and non-Eclipse projects are in gray. This was to make it easier to grasp the scope and comprehensiveness of the Eclipse IoT and Edge ecosystem at a glance. Every project included in the matrix is worth your consideration when building an Edge Computing solution.
Ecosystem Overview
Broadly speaking, the projects featured in the matrix belong to one of three categories:
- Infrastructure
- Protocols and frameworks
- Edge Applications
In the infrastructure category, we find familiar and less familiar platforms used to run applications or manage the networking and storage capabilities they require. This, of course, includes Kubernetes but also the OpenStack and StarlingX duo, as well as the Eclipse ioFog platform. The Linux Foundation’s Projet Eve also belongs to this category. Some projects have a fairly wide scope. For example, the ONAP project encompasses the orchestration, management, and automation of network and edge computing services. Others, such as Eclipse Hono and Eclipse hawkBit, have a tight focus on specific aspects of the solution — device connectivity and software updates, respectively.
The protocols and frameworks category features projects used to build edge applications. There, we find popular implementations of existing protocols such as MQTT (Eclipse Mosquitto, Eclipse Paho) and DDS (Eclipse Cyclone DDS). There are also recent innovations, such as the Eclipse zenoh protocol. Of course, at this point in time, the Eclipse Foundation is at the center of the Cloud-Native Java ecosystem, being the home of the Jakarta EE and Microprofile communities.
Finally, the Edge Applications category contains projects that run on edge infrastructure and are built with the applications and frameworks of the previous category. A typical example is the successful Eclipse Kura project, used in many open-source and commercial IoT gateways. Another example is EdgeX Foundry from LF Edge (Linux Foundation), a set of microservices enabling IoT devices and applications integration. Both support multiple IoT protocols.
Beyond the Matrix
Look again at the matrix. Consider how the projects occupy the space defined by the two continuums. To build solutions implementing the EdgeOps approach properly, you must pick several components from the three categories I described. Moreover, there are several technologies not covered by the matrix such as operating systems and development tools.
The EdgeOps matrix clarifies that the open-source ecosystem contains everything you need to build robust IoT and edge computing solutions. However, commercial products built on top of the same components provide additional features, ease of use, and support that the open-source community cannot deliver. How to pick from the plethora of products currently available, then? Generally speaking, commercial products extending an open-source project are more sustainable over the long term and provide assurances against vendor lock-in.
My next post will discuss how you can leverage EdgeOps in real projects. If you cannot wait and wish to learn more about EdgeOps right away, please look at our white paper.
All Edge of Things contributors belong to Eclipse Foundation member organizations or are Foundation staff.
