[hu3]

I expected more mentions of Vitess, which honestly looks like some kind of alien black magic from what I saw while consulting for a client this year.

But I guess not much else happened to it other than PlanetScale.

[leetrout]

Which part most impressed you and which part seems like magic? Their devs / contributors are active on here...

[hu3]

edit: not sure why the downvotes (-3 so far) since I just stated my experience on the project. There must be something blatantly wrong in what I wrote and I would appreciate criticism.

    --------

An architect demoed the failure of a shard and the automatic promotion of its backup shard to main, in production. They actually test their failure models.

As I see it, sharding is not very hard. HA is not very hard given a reasonable SLA. But sharding with HA on a large setup that actually works is pretty hard.

Another thing that stuck in my mind was their high throughput-per-provisioned-hardware ratio. With not much hardware they were pulling 80k queries per second with room to spare.

Although I have to say, that's not much compared to GitHub which pulls 1.2 million queries/sec on Vitess [0].

[0] https://github.blog/2021-09-27-partitioning-githubs-relation...

[samlambert]

I think its more about the HN community not wanting to hear that anything other than Postgres works.

[skunkworker]

I would love to use Vitess, but it doesn’t support Postgres at the moment. And that’s a non-starter unfortunately.

[ransom1538]

All major companies are moving to Vitess. The battle is over. No one at scale uses Postgres.

[sbmthakur]

Any reference for this?

[anaganisk]

Uber - https://eng.uber.com/postgres-to-mysql-migration/