Amazon recently announced RDS Aurora a new addition to their database as a service offerings.
Here’s Mark Callaghan’s take on what’s happening under the hood and thoughts from Fusheng Han.
Amazon is uniquely positioned with RDS to take on offerings like Clustrix. So it’s definitely worth reading Dave Anselmi’s take on Aurora.
Join 28,000 others and follow Sean Hull on twitter @hullsean.
1. Big availability gains
One of the big improvements that Aurora seems to offer is around availability. You can replicate with aurora, or alternatively with MySQL binlog type replication as well. They’re also duplicating data two times in three different availability zones for six copies of data.
All this is done over their SSD storage network which means it’ll be very fast indeed.
2. SSD means 5x faster
The Amazon RDS Aurora FAQ claims it’ll be 5x faster than equivalent hardware, but making use of it’s proprietary SSD storage network. This will be a welcome feature to anyone already running on MySQL or MySQL for RDS.
3. Failover automation
Unplanned failover takes just a few minutes. Here customers will really be benefiting from the automation that Amazon has built around this process. Existing customers can do all of this of course, but typically require operations teams to anticipate & script the necessary steps.
Related: Will Oracle Kill MySQL?
4. Incremental backups & recovery
The new Aurora supports incremental backups & point-in-time recovery. This is traditionally a fairly manual process. In my experience MySQL customers are either unaware of the feature, or not interested in using it due to complexity. Restore last nights backup and we avoid the hassle.
I predict automation around this will be a big win for customers.
Check out: Are SQL Databases dead?
5. Warm restarts
RDS Aurora separates the buffer cache from the MySQL process. Amazon has probably accomplished this by some recoding of the stock MySQL kernel. What that means is this cache can survive a restart. Your database will then start with a warm cache, avoiding any service brownout.
I would expect this is a feature that looks great on paper, but one customers will rarely benefit from.
The FAQ says point-in-time recovery up to the last five minutes. What happens to data in those five minutes?
Presumably aurora duplication & read-replicas provide this additional protection.
If Amazon implemented Aurora as a new storage engine, doesn’t that mean new code?
As with anything your mileage may vary, but Innodb has been in the wild for many years. It is widely deployed, and thus tested in a variety of environments. Aurora may be a very new experiment.
Will real-world customers actually see 500% speedup?
Again your mileage may vary. Lets wait & see!
Related: 5 Things toxic to scalability