How Does edge Service Mesh Work?

The edge Service Mesh is intended to unify all the microservices running on mimOE nodes within a given mimOE Cluster under a single organizational unit. As the name implies, this organizational unit is the edge Service Mesh and can be inspected accordingly.

As mentioned previously in the section What Does edge Service Mesh Do?, mimOE microservices are organized within an edge Service Mesh according to the predefined cluster types, Network, Account or Proximity.

Figure 1: The edge Service Mesh groups nodes according to 3 types of clusters

You can read the details of the Service Mesh Network, Account and Proximity types in the Key Concepts section of this document here.

In addition to unifying the microservices running on various mimOE clusters; event, and log information about the activities of the microservices can be accessed using the edge Service Mesh.

Registering a microservice to the edge Service Mesh is automatic. Developers do not have to do anything special to have an edge node, and subsequently the microservices running on the given node, be part of a particular edge Service Mesh.

Developers gather information about the state of and the activities within the edge Service Mesh by working with the mimik Edge Node Discovery API and the mimOE Context Object. The mimOE Context Object is intrinsic to all microservices running under the mimOE Runtime. (The particulars of mimik Edge Node Discovery API and the mimOE Context Object are discussed in the Key Concepts section of the Developer Documentation.)