Need advice about which tool to choose?Ask the StackShare community!
Amazon RDS for Aurora vs GenieDB: 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; GenieDB: Multi-master, multi-cloud, geo-distributed MySQL database. GenieDB’s DBaaS uses multi-master replication and multi-regional distribution on multiple cloud infrastructures (Amazon AWS, IBM Softlayer, DigitalOcean, Rackspace Cloud, and Google Cloud) to help reduce latency, eliminate downtime, and easily scale your database.
Amazon RDS for Aurora and GenieDB can be primarily classified as "SQL Database as a Service" tools.
Some of the features offered by Amazon RDS for Aurora are:
- High Throughput with Low Jitter
- Push-button Compute Scaling
- Storage Auto-scaling
On the other hand, GenieDB provides the following key features:
- Multi-master replication with auto-conflict resolution
- Geo-distribution across multiple regions and cloud providers using eventual consistency model with geo-compliance
- Auto-recovery and healing with re-synchronization
Using on-demand read/write capacity while we scale our userbase - means that we're well within the free-tier on AWS while we scale the business and evaluate traffic patterns.
Using single-table design, which is dead simple using Jeremy Daly's dynamodb-toolbox library
Pros of Amazon Aurora
- MySQL compatibility14
- Better performance12
- Easy read scalability10
- Speed9
- Low latency read replica7
- High IOPS cost2
- Good cost performance1
Pros of GenieDB
Sign up to add or upvote prosMake informed product decisions
Cons of Amazon Aurora
- Vendor locking2
- Rigid schema1