harshitgangal

Re:SPQR 2.6.0 with Multicolumn Sharding on Sunday May 25, 2025 @07:20PM (#44092221)

Yes, Vitess supports sharding out of the box. It’s actually one of its core design goals.

I am a maintainer on the project, and Vitess provides native support for sharded query routing, resharding, and cluster management at scale.

Re:Show HN: A Database Written in Golang on Thursday February 27, 2025 @10:05AM (#43194997)

Yes! The founders of PlanetScale were the co-creators of Vitess at YouTube, where it was built to handle MySQL scalability. PlanetScale builds on Vitess but offers a managed, developer-friendly experience.

Re:Velox: Meta's Unified Execution Engine [pdf] on Tuesday March 26, 2024 @02:50AM (#39824869)

When Vitess was donated to CNCF, there was an internal push from within Google to migrate everything to Spanner.

I do not know any other reason.

Disclaimer: Vitess Maintainer

Vitess 18 GA Release

Posted by harshitgangal on Tuesday November 07, 2023 @09:03AM
from the vitess.io dept.

https://vitess.io/blog/2023-11-07-announcing-vitess-18/

( Read More... | no comments | on HN )

Re:Vercel Service Markup on Wednesday May 03, 2023 @01:53AM (#35798513)

Likewise in Vitess. It is architecturally possible to add 100% compatibility :)

Re:Scaling Databases at Activision [pdf] on Tuesday April 25, 2023 @10:00AM (#35700591)

just the right time to ask this question. We have an RFC open to add support for foreign keys in Vitess https://github.com/vitessio/vitess/issues/12967

Re:Connection Pooling in Vitess on Tuesday March 28, 2023 @11:03AM (#35342223)

Learn what Vitess does to allow modifying MySQL system settings on a connection from the pool.

Connection Pooling in Vitess

Posted by harshitgangal on Tuesday March 28, 2023 @11:03AM
from the planetscale.com dept.

https://planetscale.com/blog/connection-pooling

( Read More... | 1 comment | on HN )

Re:One million queries per second with MySQL on Friday September 02, 2022 @04:43AM (#32688266)

Sequences actual use is for sharded keyspace. For unsharded you can just continue to use auto_increment.

Maybe your application has some special logic which is complex enough to unwind. I am just clarifying for the second statement.

Re:One million queries per second with MySQL on Thursday September 01, 2022 @03:46PM (#32682019)

Disclaimer: I am a Vitess Maintainer.

Please find my answer inline

1. You can't have single database view of all shards

- Vitess does query planner and routing for the application so application does not have to know about shards. Yes, Vitess gives a view of a single database.

2. No distributed ACID

- This has been talked a lot feature and it is in our roadmap to provide. Currently, we have a twoPC implementation which we do not recommend for production use. Right now the users of vitess either choose their sharding key in such a way that all the queries in a transaction goes to single shard or the application can handle best effort multi shard transaction.

3. No distributed JOINs

- Vitess does support distributed joins, aggregation, subqueries and other complex queries. Vitess thrive to be 100% Mysql compatible. If anyone encouter such query, a github issue helps in knowing and prioritizing.