Need advice about which tool to choose?Ask the StackShare community!
Amazon RDS for Aurora vs Serverless: What are the differences?
Amazon RDS for Aurora: MySQL and PostgreSQL compatible relational database with several times better performance. Amazon Aurora is a MySQL-compatible, relational database engine that combines the speed and availability of high-end commercial databases with the simplicity and cost-effectiveness of open source databases. Amazon Aurora provides up to five times better performance than MySQL at a price point one tenth that of a commercial database while delivering similar performance and availability; Serverless: The most widely-adopted toolkit for building serverless applications. Build applications comprised of microservices that run in response to events, auto-scale for you, and only charge you when they run. This lowers the total cost of maintaining your apps, enabling you to build more logic, faster. The Framework uses new event-driven compute services, like AWS Lambda, Google CloudFunctions, and more.
Amazon RDS for Aurora and Serverless are primarily classified as "SQL Database as a Service" and "Serverless / Task Processing" tools respectively.
"MySQL compatibility " is the primary reason why developers consider Amazon RDS for Aurora over the competitors, whereas "API integration " was stated as the key factor in picking Serverless.
Serverless is an open source tool with 30.9K GitHub stars and 3.43K GitHub forks. Here's a link to Serverless's open source repository on GitHub.
According to the StackShare community, Serverless has a broader approval, being mentioned in 117 company stacks & 44 developers stacks; compared to Amazon RDS for Aurora, which is listed in 121 company stacks and 31 developer stacks.
When adding a new feature to Checkly rearchitecting some older piece, I tend to pick Heroku for rolling it out. But not always, because sometimes I pick AWS Lambda . The short story:
- Developer Experience trumps everything.
- AWS Lambda is cheap. Up to a limit though. This impact not only your wallet.
- If you need geographic spread, AWS is lonely at the top.
Recently, I was doing a brainstorm at a startup here in Berlin on the future of their infrastructure. They were ready to move on from their initial, almost 100% Ec2 + Chef based setup. Everything was on the table. But we crossed out a lot quite quickly:
- Pure, uncut, self hosted Kubernetes — way too much complexity
- Managed Kubernetes in various flavors — still too much complexity
- Zeit — Maybe, but no Docker support
- Elastic Beanstalk — Maybe, bit old but does the job
- Heroku
- Lambda
It became clear a mix of PaaS and FaaS was the way to go. What a surprise! That is exactly what I use for Checkly! But when do you pick which model?
I chopped that question up into the following categories:
- Developer Experience / DX 🤓
- Ops Experience / OX 🐂 (?)
- Cost 💵
- Lock in 🔐
Read the full post linked below for all details
Pros of Amazon Aurora
- MySQL compatibility14
- Better performance12
- Easy read scalability10
- Speed8
- Low latency read replica7
- High IOPS cost2
- Good cost performance1
Pros of Serverless
- API integration14
- Supports cloud functions for Google, Azure, and IBM7
- Lower cost2
- Openwhisk1
- Auto scale1
Sign up to add or upvote prosMake informed product decisions
Cons of Amazon Aurora
- Vendor locking2
- Rigid schema1