Re:Why Google’s Spanner Database Won’t Do as Well as Its Clone
by knicholes on Wednesday February 15, 2017 @04:00PM
(#13655301)
I'm not sure, but it looks like maybe AWS already has... https://aws.amazon.com/rds/
[ Parent
| on HN ]
Re:Why Google’s Spanner Database Won’t Do as Well as Its Clone
by daenney on Wednesday February 15, 2017 @04:23PM
(#13655464)
You can't compare that to Spanner. RDS is a product that helps you manage/scale something like MySQL for you. It would compare to CloudSQL in the Google portfolio.
However, they have their own database engine called Aurora, which is what you actually get when you select MySQL or Postgres for RDS and provides much better throughput and replication behaviour. You can also only have up to 15 Aurora replicas whereas Spanner goes far far beyond that.
Re:Why Google’s Spanner Database Won’t Do as Well as Its Clone
by bdcravens on Thursday February 16, 2017 @03:07AM
(#13658381)
Aurora uses a MySQL-compliant API, but non-Aurora MySQL RDS instances are not using Aurora. Those instances are just managed MySQL. Ditto for Postgres (Aurora Postgres is in closed beta)
Re:Why Google’s Spanner Database Won’t Do as Well as Its Clone
by duskwuff on Wednesday February 15, 2017 @04:24PM
(#13655471)
Generic RDS is just hosted MySQL. A better comparison might be Aurora:
Re:Why Google’s Spanner Database Won’t Do as Well as Its Clone
by lobster_johnson on Wednesday February 15, 2017 @07:31PM
(#13656920)
Still a very far-fetched comparison. Aurora is "just" a read replica system underneath a fairly vanilla MySQL. Better than MySQL, but miles away from the sophistication of Spanner.