You could just install a Galera cluster on DO and it'd function similarily, and tbh, that is possibly what they did.
Ignoring the benchmark BS [which is almost always BS] basically they are offering:
> With storage replicated both within and across three Availability Zones, along with an update model driven by quorum writes, Amazon Aurora is designed to deliver high performance and 99.99% availability while easily and efficiently scaling to up to 64 TB of storage.
Galera is quorum writes [basically], can scale to ~6 nodes pretty effectively [more than 6 you run into issues with write performance imho. This would be a 2/2/2 for 3 availability zone setup].
Galera's synchronous write process means you want everything near each other geographically, so 3 AZs in the same region would make perfect sense.
> Along the way, they verified that each Amazon Aurora instance is able to deliver on our performance target of up to 100,000 writes and 500,000 reads per second, along with a price to performance ratio that is 5 times better than previously available.
That is literally the read/write ratio you'll see on a 6 node Galera cluster. Reads scale per-node [reads are local], but writes don't [every node has to perform the write + the replication overhead].
So yeah, you can set something similar up with any provider with 3 geographically near DCs.
Ignoring the benchmark BS [which is almost always BS] basically they are offering:
> With storage replicated both within and across three Availability Zones, along with an update model driven by quorum writes, Amazon Aurora is designed to deliver high performance and 99.99% availability while easily and efficiently scaling to up to 64 TB of storage.
Galera is quorum writes [basically], can scale to ~6 nodes pretty effectively [more than 6 you run into issues with write performance imho. This would be a 2/2/2 for 3 availability zone setup].
http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concep...
Galera's synchronous write process means you want everything near each other geographically, so 3 AZs in the same region would make perfect sense.
> Along the way, they verified that each Amazon Aurora instance is able to deliver on our performance target of up to 100,000 writes and 500,000 reads per second, along with a price to performance ratio that is 5 times better than previously available.
That is literally the read/write ratio you'll see on a 6 node Galera cluster. Reads scale per-node [reads are local], but writes don't [every node has to perform the write + the replication overhead].
So yeah, you can set something similar up with any provider with 3 geographically near DCs.
https://www.digitalocean.com/features/reliability/
DO has that setup in NYC and AMS, at least I assume NYC1/2/3 AMS1/2/3 are different AZ equivalents.