Skip to main content

AWS Solutions Library

Guidance for Distributed Order Management on AWS

Overview

This Guidance helps you build an order management system (OMS) on AWS using cloud-native services. By building OMS on the cloud, you can incorporate an event-based workflow to help streamline orders, from order entry to fulfillment. This Guidance also helps you manage and analyze data within your OMS so you can generate insights to improve your customer experience. 

How it works

These technical details feature an architecture diagram to illustrate how to effectively use this solution. The architecture diagram shows the key components and their interactions, providing an overview of the architecture's structure and functionality step-by-step.

Download the architecture diagram

Well-Architected Pillars

The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.

This architecture follows a microservices approach, meaning that services are decoupled from one another. This allows you to make small, frequent, and reversible changes to the architecture. Additionally, if one component of the architecture fails, it will not affect other components.  

Read the Operational Excellence whitepaper 

Data is encrypted at rest in DynamoDB and Aurora. 

Read the Security whitepaper 

This architecture uses stateless compute, meaning that data is not stored on servers so that servers can perform other functions. It also uses a decoupled architecture so that the function of one service is not altered by the function of another. 

Read the Reliability whitepaper 

This architecture uses DynamoDB, which delivers response times that can be measured in single-digit milliseconds for most cases. If you need response times in microseconds, you can use DynamoDB Accelerator (DAX).

Read the Performance Efficiency whitepaper 

This architecture is an internal application, so data transfer charges between Availability Zones within an AWS Region will be lower compared to an external application. 

Read the Cost Optimization whitepaper 

This architecture uses serverless services, which helps ensure that applications only use the exact amount of resources needed. 

Read the Sustainability whitepaper 

Disclaimer

The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.

References to third-party services or organizations in this Guidance do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy the architecture.