Looking for Feedback on My Multi-Region Architecture Design

0
8
Asked By CuriousCat123 On

I'm working on a multi-region architecture for my organization's application and would love some feedback. We're using Akamai for both WAF and CDN to manage routing between two regions: us-east-1 and us-west-2. The user interface is a static React site hosted on S3, and we'll be utilizing S3 multi-region access points for latency-based routing and failover, which Akamai will use as a global endpoint. For the backend, we're deploying our microservices on EKS with an API Gateway in front and an Application Load Balancer (ALB) serving as the ingress for EKS, structured as API Gateway -> VPC Link v2 -> ALB -> EKS. For our database, we're opting for Aurora DSQL, with read/writer instances in both east and west regions while having east as the witness region. We'll have health check APIs for both the core microservices and database. If health checks fail in one region, Akamai will reroute traffic to the other healthy region. I'd appreciate any thoughts on this architecture and the failover strategy!

4 Answers

Answered By DataDive77 On

Why go with DSQL? If you're an AWS-only shop per leadership's orders and need auto failover, you might want to consider a different approach. You mentioned Postgres—is there a way to optimize that further?

Answered By TechWizard99 On

Your design looks promising, especially with the multi-region S3 access points combined with Akamai's global routing. Just make sure to load-test the regional failover to ensure Aurora behaves correctly if one writer region goes down.

Answered By CloudEnthusiast42 On

Got a couple of questions for you: Why involve Akamai when AWS regions are tightly connected? Simplifying the network could save you money and speed things up. Also, if you're concerned about costs, Aurora DSQL might be more expensive than a global database option, so clarify your RTO and RPO requirements before going that route.

Answered By Overthinker88 On

Honestly, it seems a bit over-engineered with the combo of API Gateway, ALB, and EKS. If you're bound to Kubernetes, can you elaborate on your use case? That’ll help others give more targeted feedback.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.