About This Architecture

Multi-AZ eCommerce platform combining Medusa.js headless commerce backend with Next.js frontend on Vercel, deployed across two AWS availability zones for high availability. User traffic flows through Vercel's CDN to Next.js, then through Internet Gateway, WAF, and ALB to Medusa.js servers in private subnets, which connect to RDS PostgreSQL with read replicas, ElastiCache Redis, and Meilisearch for search. The architecture integrates external payment gateways (CMI), fulfillment services (WFC), and cash-on-delivery options while monitoring all components via CloudWatch. This pattern demonstrates production-grade separation of concerns: stateless API tier, managed data services, and edge-cached frontend for optimal performance and cost efficiency. Fork and customize this diagram on Diagrams.so to match your payment processors, fulfillment partners, or regional requirements.

People also ask

How do I architect a scalable eCommerce platform using Medusa.js on AWS with high availability and external payment integrations?

This diagram shows a production eCommerce architecture spanning two AWS availability zones with Medusa.js API servers in private subnets, RDS PostgreSQL primary-standby replication, ElastiCache for caching, and Meilisearch for search. Traffic flows through Vercel's CDN to Next.js frontend, then through WAF and ALB to Medusa.js, which integrates CMI payment gateway, cash-on-delivery, and WFC fulfil