3 ms·
I believe the issue goes much deeper. Google itself did not have a scalable SQL DB when App Engine first came out. Spanner was still being designed. Even if Goo
by kccqzy 3y ago
I believe the issue goes much deeper. Google itself did not have a scalable SQL DB when App Engine first came out. Spanner was still being designed. Even if Google understood that customers wanted a SQL DB, it could not give them that.
- vineyardmike 3y agoBut lost people don’t need a scalable database. They need Postgres for 200 rows. Or really just SQLite but over the network.
- barrkel 3y agoGoogle was running MySQL in different flavours and configurations before Spanner. I suspect strategy tax (knowing Spanner was coming along eventually) might have been a reason for not offering that as a managed option though.
- hn_throwaway_99 3y agoWhich actually goes to the heart of the issue. Who cares what Google had? MySQL and Postgres existed - Amazon RDS first came out in 2009, and you could run DBs on EC2 before that. Google famously uses lots of custom versions of infrastructure software while the rest of the world uses something else. Obviously that has served then extremely well, but the rest of the world wants stuff they are familiar with. It really took Google years to fully grasp that.