Performant Architectures Flashcards
Best practices for performant architecture
performant storage and databases
apply caching
for elasticity and scalability
static content
offload to s3 instead of keeping it on servers. takes the load off your websever. EBS only used to serve dynamic content
Use cases for Amazon RDS
Complex transactions
medium to high query or wite rate
no more than a single worker node(master) per shard
high durability(also available in dynamo DB)
Do not use RDS when
Massive read write rates
sharding
simple get put
RDBMS customization
Dynamo DB is suited for
key value access patterns
Dynamo DN
You don’t specify how much space you need. It grows as your data footprint changes
What throughput do you configure in Dynamo DB
RCU and WCU.
Read capacity unit. ( 1 RCU = 1 strongly consistent per second, 2 eventually consistent read per second) 4KB in size
1 WCU 1KB in size
Dynamo DB scales the table as per the requirement
cloudfront can be used for both static and dynamic
You can seve with TTL of zero. It is not for caching . The read and write is happnning over AWS backbone network and not on internet.
cloudfront dynamic content origin
ELB or EC2, http servers
cloudfront static content origin
S3
Implement elasticity with ASG, ELB and cloudwatch
Cloudwatch monitor instances
raise alarms when metrics exceed threashold
SNS intercepted by ASG.
What can cloudwatch monitor
CPU, queue size, network utilization
storage solution for unstructured data that is generally preferred
S3