Re:PlanetScale – Database for Developers
by adamfeldman on Tuesday May 18, 2021 @01:51PM
(#27198397)
Branching wasn't mentioned in the linked blog post, but I assume that is what the parent comment is excited about: https://docs.planetscale.com/concepts/branching
Indeed, thank you!
Re:PlanetScale – Database for Developers
by eurasiantiger on Tuesday May 18, 2021 @06:59PM
(#27202378)
It doesn’t solve the N+1 queries problem in a generic way. That is a major hurdle in scaling complexity-wise, which in turn is often deeply coupled with business realities.
More to the point, it probably cannot solve it efficiently at all, since it is not a graph database and thus cannot be paired with a generic GraphQL resolver (would generate join queries instead of lookups across edges) and a stack of generated static queries in the backend (no need to allow generic queries, just make it possible to write queries once and only once).
Re:PlanetScale – Database for Developers
by ransom1538 on Tuesday May 18, 2021 @07:58PM
(#27202898)
"It doesn’t solve the N+1 queries problem in a generic way."
IMHO, this isn't trying to solve people looping queries. The fastest way to solve this is to not loop queries.
This solves auto-sharding (well vitness did). See slack architects comment below.
Re:PlanetScale – Database for Developers
by eurasiantiger on Friday May 21, 2021 @08:07AM
(#27232993)
You are misunderstanding the nature of the problem and how it arises in any system that uses multiple entities to represent real-world entities.
Re:PlanetScale – Database for Developers
by manigandham on Tuesday May 18, 2021 @11:11PM
(#27204110)
How's that related? This is a commercial managed version of Vitesse - which is an open-source system for horizontally scaling MySQL: https://vitess.io/
That is: how can I pair a brand new frontend preview deploy, with a serverless database with the specific schema my new feature needs?
This technology makes the whole serverless stack feel complete.