Skip to content

Instantly share code, notes, and snippets.

@xeoncross
Created February 12, 2020 17:54
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save xeoncross/1d12f85dc61a95080462f8392cef7ebb to your computer and use it in GitHub Desktop.
Save xeoncross/1d12f85dc61a95080462f8392cef7ebb to your computer and use it in GitHub Desktop.
Amazon AWS Aurora Serverless - Summary

I have a pretty constant-use case in mind for collecting client metrics with different loads and spikes throughout the day and am mostly interested in paying a little extra to not have to manage the RDS/Aurora server instances. I basically just need a k/v store but need to do report queries/scans so DynamoDB isn’t a good fit. (COUNT(*) FROM, SUM, etc..)

Slow start

Looks like a minimum of 5 minutes of usage each time the database is activated and I’m pretty sure my load will never let the database shutdown so that might solve the cold-start issue.

https://aws.amazon.com/rds/aurora/faqs/?nc=sn&loc=6

Scaling

The only thing I’m concerned about is it not handling spikes. Seems to “wait” until all the table locks, long-running queries, etc.. are finished before trying to “scale” up.

Each Aurora Serverless DB cluster requires two AWS PrivateLink endpoints. If you reach the limit for AWS PrivateLink endpoints within your VPC, you can’t create any more Aurora Serverless clusters in that VPC.

Limits

Each Aurora Serverless DB cluster requires two AWS PrivateLink endpoints. If you reach the limit for AWS PrivateLink endpoints within your VPC, you can't create any more Aurora Serverless clusters in that VPC.

https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverless.html#aurora-serverless.limitations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment