AWS prescriptive-guidance documentation change
Summary
Updated image paths, fixed apostrophe formatting, changed table formatting by removing checkmarks from AWS service pattern support, and modified section headings for clarity.
Security assessment
Changes involve typo corrections (apostrophe), image path updates, table formatting changes (removed checkmarks), and heading rephrasing. No security vulnerabilities, configurations, or features are mentioned or modified. The removal of pattern support indicators in the table doesn't introduce or mitigate security risks.
Diff
diff --git a/prescriptive-guidance/latest/mes-on-aws/integration.md b/prescriptive-guidance/latest/mes-on-aws/integration.md index 847b19c01..27723402d 100644 --- a//prescriptive-guidance/latest/mes-on-aws/integration.md +++ b//prescriptive-guidance/latest/mes-on-aws/integration.md @@ -19 +19 @@ The following functional patterns provide guidelines on selecting the right tech -In a synchronous communications pattern, the calling service is blocked until it receives a response from the endpoint. The endpoint can typically call other services for additional processing. MES requires synchronous communications for latency-sensitive transactions. For example, consider a continuous production line where one user completes an operation on an order. The next user would expect to see that order immediately arrive for the next operation. Any delay in such transactions could negatively impact the product’s cycle time and plant performance KPIs, and could cause additional wait time and under-utilization of resources. +In a synchronous communications pattern, the calling service is blocked until it receives a response from the endpoint. The endpoint can typically call other services for additional processing. MES requires synchronous communications for latency-sensitive transactions. For example, consider a continuous production line where one user completes an operation on an order. The next user would expect to see that order immediately arrive for the next operation. Any delay in such transactions could negatively impact the product's cycle time and plant performance KPIs, and could cause additional wait time and under-utilization of resources. @@ -21 +21 @@ In a synchronous communications pattern, the calling service is blocked until it - + @@ -27 +27 @@ In this communication pattern, the caller doesn't wait for a response from the e - + @@ -31 +31 @@ In this communication pattern, the caller doesn't wait for a response from the e -The publish-subscribe (pub/sub) pattern further extends asynchronous communications. Managing interdependent communications can become challenging as the MES matures and the number of microservices grows. You might not want to change a caller service every time you add a new service that has to listen to it. The pub/sub pattern solves this by enabling asynchronous communications among multiple microservices without tight coupling. In this pattern, a microservice publishes event messages to a channel that subscriber microservices can listen to. Therefore, when you add a new service, you subscribe to the channel without changing the publishing service. For example, a production report or operation-complete transaction might update several log and transaction history records. Instead of modifying these transactions whenever you add new logging services for machines, labor, inventory, external systems, and so on, you can subscribe each new service to the original transaction's message and handle it separately. +The publish/subscribe (pub/sub) pattern further extends asynchronous communications. Managing interdependent communications can become challenging as the MES matures and the number of microservices grows. You might not want to change a caller service every time you add a new service that has to listen to it. The pub/sub pattern solves this by enabling asynchronous communications among multiple microservices without tight coupling. In this pattern, a microservice publishes event messages to a channel that subscriber microservices can listen to. Therefore, when you add a new service, you subscribe to the channel without changing the publishing service. For example, a production report or operation-complete transaction might update several log and transaction history records. Instead of modifying these transactions whenever you add new logging services for machines, labor, inventory, external systems, and so on, you can subscribe each new service to the original transaction's message and handle it separately. @@ -33 +33 @@ The publish-subscribe (pub/sub) pattern further extends asynchronous communicati - + @@ -41 +41 @@ AWS offers multiple [serverless services](https://aws.amazon.com/serverless/) th -**AWS service** | **Description** | **Supports pattern** +AWS service| Description| Supports pattern @@ -44,6 +44,6 @@ AWS offers multiple [serverless services](https://aws.amazon.com/serverless/) th -[Amazon API Gateway](https://aws.amazon.com/api-gateway/) | Enables microservices to access data, business logic, or functionality from other microservices. API Gateway accepts and processes concurrent API calls for all three communication patterns. | ✓ | ✓ | ✓ -[AWS Lambda](https://aws.amazon.com/lambda/) | Provides serverless, event-driven compute functionality to run code without managing servers. Businesses can use Lambda to decouple, process, and pass data between other AWS services such as databases and storage services. | ✓ | ✓ | ✓ -[Amazon Simple Notification Service (Amazon SNS)](https://aws.amazon.com/sns/) | Supports application-to-application (A2A) and application-to-person (A2P) messaging. A2A provides high-throughput, push-based messaging between distributed systems, microservices, and serverless applications. A2P functionality lets you send messages to people with SMS texts, push notifications, and email. | | ✓ | ✓ -[Amazon Simple Queue Service (Amazon SQS)](https://aws.amazon.com/sqs/) | Lets you send, store, and receive messages between software components at any volume without losing messages or requiring other services to be available. | | ✓ | ✓ -[Amazon EventBridge](https://aws.amazon.com/eventbridge/) | Provides real-time access to events caused by changes in data in a microservice or an AWS service within a microservice without writing code. You can then receive, filter, transform, route, and deliver this event to the target. | | ✓ | ✓ -[Amazon MQ](https://aws.amazon.com/amazon-mq/) | Managed message broker service that streamlines the setup, operation, and management of message brokers on AWS. Message brokers allow software systems, which often use different programming languages on various platforms, to communicate and exchange information. | | | ✓ +[ Amazon API Gateway](https://aws.amazon.com/api-gateway/)| Enables microservices to access data, business logic, or functionality from other microservices. API Gateway accepts and processes concurrent API calls for all three communication patterns.| | | +[AWS Lambda](https://aws.amazon.com/lambda/)| Provides serverless, event-driven compute functionality to run code without managing servers. Businesses can use Lambda to decouple, process, and pass data between other AWS services such as databases and storage services.| | | +[Amazon Simple Notification Service (Amazon SNS)](https://aws.amazon.com/sns/)| Supports application-to-application (A2A) and application-to-person (A2P) messaging. A2A provides high-throughput, push-based messaging between distributed systems, microservices, and serverless applications. A2P functionality lets you send messages to people with SMS texts, push notifications, and email.| | | +[Amazon Simple Queue Service (Amazon SQS)](https://aws.amazon.com/sqs/)| Lets you send, store, and receive messages between software components at any volume without losing messages or requiring other services to be available.| | | +[Amazon EventBridge](https://aws.amazon.com/eventbridge/)| Provides real-time access to events caused by changes in data in a microservice or an AWS service within a microservice without writing code. You can then receive, filter, transform, route, and deliver this event to the target.| | | +[Amazon MQ](https://aws.amazon.com/amazon-mq/)| Managed message broker service that streamlines the setup, operation, and management of message brokers on AWS. Message brokers allow software systems, which often use different programming languages on various platforms, to communicate and exchange information.| | | @@ -59 +59 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Determining the best purpose-built technology +Determining the best purpose-built technology for MES @@ -61 +61 @@ Determining the best purpose-built technology -Using cloud-native technologies to manage microservices +Using cloud-native technology to manage, orchestrate, and monitor microservices for MES