About This Architecture

Global Flight Data Exchange using Solace Event Mesh integrates multi-region brokers across US-East, EU-West, APAC, and ME with AWS services including ECS, Lambda, MSK Kafka, RDS Aurora, and DynamoDB. Publishers like airlines, airports, booking agents, and crew systems connect via Solace PubSub+ to internal subscribers including Order Service, Flight Events Lambda, Booking Service, and Crew Events Lambda across two availability zones. The architecture decouples external partners from internal systems through event-driven patterns, enabling real-time flight data synchronization while maintaining security boundaries via VPC isolation, WAF, and IAM. Fork this diagram on Diagrams.so to customize broker regions, add additional Lambda functions, or adjust subnet CIDR blocks for your flight operations platform. Consider adding Solace message VPN segmentation for multi-tenant isolation if supporting competing airlines on shared infrastructure.

People also ask

How do you design a global flight data exchange using Solace Event Mesh on AWS with multi-region brokers and internal microservices?

This diagram shows a Solace Event Mesh architecture with four regional brokers (US-East, EU-West, APAC, ME) connecting external publishers like airlines and airports to internal AWS services including ECS Order and Booking Services, Lambda Flight and Crew Events, MSK Kafka brokers, and RDS Aurora databases across two availability zones. The design decouples external partners from internal systems