Scalable Architecture for high performance and Stability
For better performance, speed, stability. We suggest for below Architecture
Part 1: EC2 INSTANCE FOR RUNNING THE WEB APPLICATION
Basic Specification: General Purpose
- Name t2.medium
- VCPU 4
- Memory 8 GB
- I/O Low to moderate
- EBS opt NO
- On Demand Hourly cost $0.186
Moderate Specification: IOPS [This supports last minute/second bidding]
- Name m4.large
- VCPU 2
- Memory 8.0 GB
- I/O Moderate
- EBS opt Yes
Higher Specification: IOPS [For high traffic and very high concurrent users at last minute bidding when needs to be stable]
- Name m4.xlarge
- VCPU 4
- Memory 16.0 GB
- I/O High
- EBS opt Yes
- On Demand Hourly cost $0.200
Part 2: RDS FOR DATABASE
We have to RDS for database instead of local DB for higher performance
Basic Specification: Provisional IOPS
- Name t2.medium
- Memory 100 GB
- IOPS No
Moderate Specification: Provisional IOPS
- Name m4.large
- · Memory 100 GB
- . IOPS 1000
Higher Specification: Provisional IOPS
- Name m4.Xlarge,m4.x2large
- · Memory 100 GB
- · IOPS 1000
Part 3 : LOADBALANCER AND AUTOSCALING
A load balancer distributes workloads across multiple compute resources, such as virtual servers. Using a load balancer increases the availability and fault tolerance of your applications. You can add and remove compute resources from your load balancer as your needs change, without disrupting the overall flow of requests to your applications.
Amazon EC2 Auto Scaling helps you ensure that you have the correct number of Amazon EC2 instances available to handle the load for your application. You create collections of EC2 instances, called Auto Scaling groups. You can specify the minimum number of instances in each Auto Scaling group, and Auto Scaling ensures that your group never goes below this size.