Implementing Travel & Hospitality Data Mesh: AWS Reference Architecture
Implementing Travel & Hospitality Data Mesh: AWS Reference Architecture
1
Implementing Travel & Hospitality Data Mesh real-time data, Secure File Transfer Protocol
(SFTP) and IoT sensors.
The travel and hospitality industries are facing new challenges when generating, accessing, and analysing data at scale. Use this new approach to build a data
Data sources are managed by the Business
platform that serves both operational and analytical needs by using domain owned design, maintained data properties, open data standards, purpose-built
databases, and extensible serverless architecture. This data delivery platform architecture helps relieve and eventually replace the on-premises data platform
2 Domain. Producers use organization-level
load, leading to cost savings and an agile environment. blueprints to provide core services such as
security, governance, and open standards.
Producers build the Operational Data Store using
External AWS Cloud Amazon DynamoDB and Amazon DynamoDB
2 Producer Domain Accounts Central IT Platform 3 Consumer Domain Accounts Accelerator (DAX) to provide consistent single-
Data
4 digit-millisecond latency performance.
Producer 1 Account – Metadata
Reservation Domain Consumer 1 Account-
Batch 5 Marketing Domain Consumer Domain uses process data sets from
AWS Glue Amazon Amazon
3 multiple producer domains based on business
1 Data Catalog Neptune DynamoDB needs. Consumers build a data mart using
Events Data Amazon Redshift Amazon
Ingestion Crawler Amazon Amazon
(Data mart) Athena
Amazon Redshift and analytics using Amazon
EMR Athena
and Governance QuickSight.
Integration
Metadata is managed via multiple services. AWS
Amazon S3 Amazon S3 Amazon S3
AWS
CloudTrail
Amazon
CloudWatch
AWS Cloud
Formation
Amazon S3
Derived Data Sets
Amazon
QuickSight 4 Glue is used for data cataloguing. Data lineage is
AWS Transfer Raw Data Raw Data Process Data (Visualization)
System of Family Batch Real Time Sets stored in Amazon Neptune. Data contracts are
Records AWS Security & Access stored in DynamoDB.
Management Services Consumer accounts 2 –
Revenue Management
Consumers use online, text-based search and
Amazon
EventBridge
AWS Step AWS Amazon
Domains
5 filtering of data sets recorded in the central data
Batch Functions Lambda DynamoDB
(ODS)
AWS AWS
AWS AWS
Consumer accounts 3..m –
catalog to collect data. They can search for
Secrets Single relevant data by name, contents, sensitivity, or
IAM KMS Other Domains such as Sales,
Manager Sign-On
Finance, Customer, Airport, other any other custom labels you have defined.
Amazon Kinesis Producer 2 Account - and Operation
Events
Loyalty Domain
AWS Lake Formation provides centralized
Amazon Amazon Amazon AWS Firewall
GuardDuty Inspector Macie Manager
7
Account(s) - Machine Learning 6 management of security, governance and auditing
AWS Data
Producer 3 Account -
policies including fine-grain permissions. It also
Exchange enables automatic schema discovery and
Engineering Domain Discovery
Amazon Amazon conversion to the required format.
IOT Sensor SageMaker Athena
Data ML (Machine Learning) is performed using Lake
Producer accounts – Other
7
Batch AWS IoT Core Amazon Crawler AWS Glue
Domains such as Digital, Athena DataBrew Formation. Use Amazon SageMaker to provide
Revenue, and HR Amazon S3 AI Services standard AI/ML models for customer
AWS Lake Formation 6 Predictive Models
segmentations and lifetime value. Other AI
AWS IoT Greengrass Events
services such as Amazon Personalize can be
utilized to get actionable insight.