▲ | sgarland 12 hours ago | |||||||||||||||||||||||||
Oh yeah, separating compute and storage by a large physical distance was a great idea that certainly had no downsides! It's so awesome that they added "Optimized Reads" as an option, which is literally just running the DB on a server with a local NVMe drive - you know, how people used to do things. The only feature that Aurora (MySQL) has that is remotely impressive is its ability to restart the DB process without losing the buffer pool. Aurora (Postgres) has no interesting differentiations. I've benchmarked both, with prod-like workloads, against some 12 year old Dell R620s I have, which have NVMe drives exposed via Ceph over Infiniband. The ancient servers handily beat Aurora and RDS on everything except when the latter had an instance type with a local NVMe drive, at which point it's just superior clock speed and memory throughput. I despise Aurora with a burning passion. AWS successfully hoodwinked companies everywhere with bullshit, and are absolutely raking in cash because of it. | ||||||||||||||||||||||||||
▲ | evanelias 7 hours ago | parent | next [-] | |||||||||||||||||||||||||
> The only feature that Aurora (MySQL) has that is remotely impressive Aurora is one of the only options if you need low-lag physical replication in a MySQL-compatible environment. That makes it operationally feasible to execute large/heavy writes or DDL which would normally cause too much replication lag on traditional (async binlog-based) MySQL replicas. Granted, there's some important fine print: long transactions will still block InnoDB purge of old row versions, and in Aurora that's cluster-wide. But in any case, personally I'd consider nearly-lag-free replication to be an important differentiator. This can be leveraged in interesting ways, for example CashApp's `spirit` OSC tool (https://github.com/block/spirit) can do online schema changes blazing-fast because it doesn't need to throttle its write rate to avoid replication lag. Scale-to-zero is also nice for dev/test environments. That said, I do agree with your overall point that Aurora was majorly over-marketed. And Amazon's capture of so much revenue in the MySQL space has been extremely detrimental for the MySQL ecosystem, especially considering Aurora's modifications are proprietary/closed-source. | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||
▲ | belter 10 hours ago | parent | prev [-] | |||||||||||||||||||||||||
> The only feature that Aurora (MySQL) has that is remotely impressive is its ability to restart the DB process I dont really care about Aurora MySQL...only Aurora Postgres, but you forgot about Parallel Query and Clones. For clones you dont pay for the extra storage for the new database, only the delta if you add new data... https://aws.amazon.com/blogs/aws/new-parallel-query-for-amaz... https://aws.amazon.com/blogs/aws/amazon-aurora-fast-database... "...AWS successfully hoodwinked companies everywhere with bullshit, and are absolutely raking in cash because of it." Really?... "How Twilio modernized its billing platform on Amazon Aurora MySQL" - https://aws.amazon.com/blogs/database/how-twilio-modernized-... "No observable Aurora downtime taken in over 5 months of experimentation, and almost 2 months of running shadow production.. Steady state metrics on over 40 accumulated days of live production data across all Aurora clusters: - Over 46 billion transaction records indexed and available, compared to less than one billion stored in the former online Redis system - 4.8 TB of data across all tables - Over 11,000 active database connections to all clusters - Less than 10 milliseconds median end-to-end transaction run latency - Less than 60 milliseconds 99th percentile end-to-end transaction run latency..." "Increasing Scalability and Reducing Costs Using Amazon Aurora Serverless with BMW" - https://aws.amazon.com/solutions/case-studies/bmw-group-auro... "FINRA CAT selects AWS for Consolidated Audit Trail" - https://aws.amazon.com/blogs/publicsector/finra-cat-selects-... | ||||||||||||||||||||||||||
|