The edgeEngine Service Mesh solves the problem of providing a way to run edge devices in a unified, discoverable, and observable manner. Service mesh technology, by nature, is intended to make it so that microservices can be grouped according to some predefined unifying schema. Also, a service mesh makes it so that the host devices on which those microservices execute can be discovered at Runtime.
The edgeEngine Service Mesh adheres to the principles of a classical service mesh as described above, but also offers the additional feature of being able to group devices and services in an ad hoc manner according to a predefined set of organizational patterns.
The edgeEngine Service Mesh allows you to cluster devices according to Account, Network, or Proximity. We discuss these three types of clusters in the Key Concepts section of this developer documentation.