Industrial edge computing
MES is critical to manufacturing operations. Some microservices or functionalities
within MES require low latency and cannot tolerate intermittent connectivity to the
cloud. These microservices are better suited to run on premises. AWS edge services
Architecture
Many MES transactions are latency-sensitive. One of the examples cited later in this guide is the production execution service. One of the functions of the production execution service is to guide the flow of work-in-progress goods. Because this is a sensitive activity, the tolerance for latency could be low, and manufacturers might need an on-premises component of this microservice.
Here is the sample architecture for this use case.

-
Amazon Elastic Kubernetes Service (Amazon EKS) for computing and Amazon Relational Database Service (Amazon RDS) for databases are hosted locally in AWS Outposts. You can also use self-managed hardware to host edge components. Some features, such as Amazon EKS Anywhere, can be used for self-managed hardware as well.
-
The edge component of these services can sync with the cloud component through an Amazon API Gateway endpoint between two container instances.
Another option is to set up a service bus between the two container instances to keep them in sync. You can use Amazon Managed Streaming for Apache Kafka (Amazon MSK) to set up such service buses.
-
Manufacturers can use the cloud components of microservices to process cases that are less sensitive to latency, such as sending updates to a PLM system for process improvement, sending confirmations to an ERP system for production, and exporting data to a data lake for reporting and analytics. Because of the cloud's economics, scale, and disaster recovery benefits, manufacturers can store data for extended periods in cloud instances of the microservice.