[SEO Subhead]
This Guidance demonstrates how to build a highly available lodging reservation system using multiple serverless compute and database services, each tailored for specific functionalities. It showcases the services employed to support the back-end of an administration portal, inventory management, and the search and book functionalities for booking engines, mobile apps, and third-party systems. With this Guidance, you can develop a consistent, low-latency inventory and booking service capable of handling any scale.
Please note: [Disclaimer]
Architecture Diagram
[Architecture diagram description]
Step 1
The property administrator access for the administrator portal is stored in an Amazon Simple Storage Service (Amazon S3) bucket and served by Amazon CloudFront.
The property administrator creates business objects such as room types, rates, shopping and booking rules, taxes, and more through Amazon API Gateway, which calls Amazon Cognito to validate credentials in the requests.
Step 2
AWS Lambda processes the configuration requests and stores them in Amazon S3 and Amazon DynamoDB. Configuration changes invoke Amazon EventBridge events for processing by other parts of the application.
Step 3
New configuration events from EventBridge invoke a Lambda function, which reads the published configuration from Amazon S3 and updates the inventory data in an Amazon Aurora serverless relational database.
Step 4
Client applications pass the searched destination to the geolocation service hosted in AWS Fargate. The geolocation service calls Amazon Location Service to determine the GeoHash. Amazon ElastiCache caches results to improve performance and reduce cost.
Step 5
Client applications use the GeoHash to call the shopping API using API Gateway and Lambda to search for properties in the location. The service retrieves the Geohash mapping from DynamoDB, a NoSQL database, and retrieves properties from the Inventory API and the dynamic pricing microservice.
Step 6
The pricing microservice provides dynamic hotel prices to the shopping service. It reads the published hotel configuration from Amazon S3.
Step 7
The booking microservice uses API Gateway, Lambda, and Amazon S3 to process client booking requests. It creates booking records in Amazon Quantum Ledger Database (Amazon QLDB). It then publishes bookings to Amazon Kinesis for consumption by the dynamic pricing microservice and other analytical or third-party applications.
Step 1
The property administrator access for the administrator portal is stored in an Amazon Simple Storage Service (Amazon S3) bucket and served by Amazon CloudFront.
The property administrator creates business objects such as room types, rates, shopping and booking rules, taxes, and more through Amazon API Gateway, which calls Amazon Cognito to validate credentials in the requests.
Step 2
AWS Lambda processes the configuration requests and stores them in Amazon S3 and Amazon DynamoDB. Configuration changes invoke Amazon EventBridge events for processing by other parts of the application.
Step 3
New configuration events from EventBridge invoke a Lambda function, which reads the published configuration from Amazon S3 and updates the inventory data in an Amazon Aurora serverless relational database.
Step 4
Client applications pass the searched destination to the geolocation service hosted in AWS Fargate. The geolocation service calls Amazon Location Service to determine the GeoHash. Amazon ElastiCache caches results to improve performance and reduce cost.
Step 5
Client applications use the GeoHash to call the shopping API using API Gateway and Lambda to search for properties in the location. The service retrieves the Geohash mapping from DynamoDB, a NoSQL database, and retrieves properties from the Inventory API and the dynamic pricing microservice.
Step 6
The pricing microservice provides dynamic hotel prices to the shopping service. It reads the published hotel configuration from Amazon S3.
Step 7
The booking microservice uses API Gateway, Lambda, and Amazon S3 to process client booking requests. It creates booking records in Amazon Quantum Ledger Database (Amazon QLDB). It then publishes bookings to Amazon Kinesis for consumption by the dynamic pricing microservice and other analytical or third-party applications.
Get Started
Well-Architected Pillars
The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.
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.
-
Operational ExcellenceRead the Operational Excellence whitepaper
EventBridge allows you to respond to events in real-time, automating responses based on changes in your AWS environment. Amazon CloudWatch monitors AWS resources and applications, providing insights into performance, operational health, and overall status so you can take proactive measures to maintain operational excellence. These services enable the building and operation of reliable, scalable, and efficient systems aligned with business objectives.
-
SecurityRead the Security whitepaper
AWS Identity and Access Management (IAM) manages access to AWS resources, defining and enforcing least privilege access and supporting multi-factor authentication (MFA) for enhanced security. Amazon Cognito simplifies user authentication and authorization, enabling secure application access while protecting user data. AWS CloudTrail provides visibility into account activity, auditing, monitoring, and compliance with security policies. EventBridge automates responses to security events, such as rotating access keys or disabling compromised resources, fortifying the overall security posture.
-
ReliabilityRead the Reliability whitepaper
EventBridge simplifies event management and routing, enabling reliable event-driven architectures. Aurora Serverless automatically scales database capacity based on demand for high availability and fault tolerance. Additionally, Fargate delivers a reliable and scalable infrastructure for containerized applications without managing servers or clusters. Location Service provides reliable and accurate location data, contributing to overall application reliability.
-
Performance EfficiencyRead the Performance Efficiency whitepaper
CloudFront efficiently delivers content by caching at edge locations, reducing latency, and improving the user experience. DynamoDB offers fast and scalable NoSQL database performance, delivering single-digit millisecond response times at any scale, making it suitable for applications with intense read/write traffic and high-performance requirements.
-
Cost OptimizationRead the Cost Optimization whitepaper
Amazon S3 provides cost-effective storage and content delivery—you pay only for the storage you use. Lambda provides serverless computing, reducing infrastructure expenses. Further, Lambda enables running code without provisioning or managing servers so that you only pay for consumed compute time.
-
SustainabilityRead the Sustainability whitepaper
Lambda and Fargate, serverless compute services, contribute to sustainability efforts by automatically provisioning and scaling resources based on actual workload demands. These services minimize waste, reduce energy consumption, and lower carbon emissions by optimizing resource utilization and eliminating idle resources.
Related Content
[Title]
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.