Scalable AWS Architecture

Component diagram

Discussion

At its core there is a customer wanting to call a service

The service has 3 tiers

1) Client side frontend application

2) Server side application processing

3) Backend state(etc) persistence

DNS

The customer calls the DNS to get to the site

1. Route53 is hosting the DNS for the site and using latency rules forwards the request to the specific regions ELB for processing

a. The has the effect of enabling DR on the site as if say for example the European region is down the Route53 sees this and routes to the next best latency destination, in this case the Australasian region

ELB

The ELB has a bunch of capabilities such as DDos protection and Https to http handoff but after its preprocessing it calls part of the target group to process the request

EC2

The EC2 instance may need to call the RDS(or other) persistence layer, where good practice is to deal with writes in a master DB and reads in replicants

Container Management

Kebernates can manage all the container images

1. The system can prepare for high load events using the Infrastructure Event Management tool