This microservice provides the administrative capability to create business objects at chain, brand, and property levels, such as room types, rates, shopping and booking rules, taxes, and so on. The configuration is published to anAmazon Simple Storage Service (Amazon S3) bucket. This decorrelates the administrative from the operational (shop and book) flows.Data is structured in Amazon DynamoDB, as described in thisblog post. Upon configuration of the publish event, the inventory microservice is called by an AWS Lambda function run from an Amazon S3 trigger. This service updates inventory data in an Amazon Aurora serverless database. Inventory counts are structured using one column per stay date over a configurable inventory horizon. This structure allows fast search and atomic write operations. This microservice is called at high volume and low latency by many clients (web, mobiles, and online travel agencies crawlers). It is used to search available properties and products. Availability is defined by inventory and business rules set up in the published configuration. Additional data is needed for property search (multi-availability) to perform a radius search. Amazon DynamoDB is used to store the property geohash. The booking microservice creates the reservation record in the Amazon Quantum Ledger Database (Amazon QLDB). QLDB supports out-of-the-box history and can be the most cost effective data store for large records at scale
