Learn Vitess - Introduction (part 1)

[@dartneer]

Talk about learning to solve Google problems with my 100 visitors per week app!! I enjoyed it though 🤣😆🤣

[@alejandrombc]

How does this behave with joined queries (that are in different servers)?. And what about a transaction that also writes to multiple servers?, is it ACID compliant?

[@yassine-sa]

For when you need to join between multiple tables in different shards, although what I'm about to say may not work in all cases, I think it's here where you should know how your applications use your database, that's why it's not a good idea to think about sharding without having a medium-sized app running in prod, not only because it's too early and it's premature optimization, also because you simply wouldn't have enough data to let you know which queries run the most, and thus what are the tables that need to live on the same instance more than others. That's just my idea, never tried it in prod, but I think it's cool

[@PlanetScale]

Great question! Vitess has support for some cross-shard operations, including some join functionality. These types of things should be avoided though, due to the performance penalty due to the network and coordination overhead. You'll see an example of vertical and horizontal sharding in some of the videos next week - stay tuned!

[@박정무-g6p]

Thank you for easy explanation about Vitess. 😊 Would you let me know what is app name that you are using to illustrate?

[@PlanetScale]

It's a custom version of Excalidraw.

[@ahmad-murery]

What if I want to join between 2 tables one resides in vtTablet1 and the other resides in vtTablet2? Will vtGate handle all the heavy lifting for parsing/optimizatig the query logics and it just uses the vtTables for storage purposes only or there is still some logics will be handled by vtTablet as well? Looking forward to continue this series. Thanks Ben!

[@PlanetScale]

Vitess supports some types of cross-shard joins, but as you probably guessed.... this is BAD for performance! Ideally, we should design our schemas so that such cases are minimized for a production DB.

[@ahmad-murery]

@@PlanetScale Thanks for the clarification. Waiting for the next episode.

[@adamwhite1431]

Nice video, thanks a lot. Nice haircut, by the way :) Looking forward to your upcoming videos!

[@PlanetScale]

Gotta be fresh for the KZbin 😎

[@abdoreda7126]

😮 cool video, appreciate explaining concepts, instead of focusing on implementations and code

[@PlanetScale]

You bet! We'll get into more "nitty-gritty" Vitess details in some of the upcoming lessons.

[@bordeux]

when next video?

[@PlanetScale]

We'll be releasing all 9 of them over the next 2-3 weeks!

[@samgraham6355]

First