About This Architecture

MyEddie's current production architecture spans two AWS accounts, integrating a load-balanced application tier with SQL Server AlwaysOn availability groups and Oracle ERP via DMS replication. The DMZ layer fronts EC2 app servers in active-active configuration, while FSx provides shared file storage and a separate data warehouse supports analytics. This design demonstrates cross-account integration patterns, database replication strategies, and separation of concerns between transactional and reporting workloads. Fork this diagram to customize for your multi-system environment, adjust replication endpoints, or document your own hybrid cloud topology. The architecture showcases best practices for disaster recovery, data consistency, and SaaS integration at enterprise scale.

People also ask

How do you design a multi-account AWS architecture that integrates SQL Server AlwaysOn with Oracle ERP using DMS replication?

This diagram shows a two-account AWS setup where MyEddie's application layer (ALB + active-active EC2 servers) connects to SQL Server AlwaysOn in Account 1, while DMS and DoubleTake replicate data to Oracle JDE in Account 2. A separate data warehouse supports analytics, demonstrating how to maintain data consistency across heterogeneous databases while isolating workloads by account.