Personally, migrations have never been painful enough to warrant this sort of product. The idea of branching databases on the other hand is really cool. Is each branch a full copy? Seems like that would lead to huge storage needs for larger databases.
Interesting, I'd be fascinated to hear what tech you use, because I've always had a really hard time with migrations.
Building PlanetScale with PlanetScale
11–20 of 23 posts
Re: Building PlanetScale with PlanetScale
#12Re: Building PlanetScale with PlanetScale
#13Re: Building PlanetScale with PlanetScale
#14PlanetScale – Database for Developers - https://news.ycombinator.com/item?id=27197873 - May 2021 (128 comments)
Re: Building PlanetScale with PlanetScale
#15Re: Building PlanetScale with PlanetScale
#16Re: Building PlanetScale with PlanetScale
#17Re: Building PlanetScale with PlanetScale
#18Earlier quoted context omitted.
I had the impression they PS was interesting because they offer serverless SQL.
I've been PlanetScale for a test drive recently, and it's a bit of both. I also think they kind of go hand-in-hand: if you have "serverless" things (or just Docker), they can come and go with connections very quickly, so picking the correct "pause time" to take the DB down for an ALTER TABLE is possible but a tiny bit awkward. Online migrations mean you never take it down and it's always available so that's kind of m…
What other differences are there vs MySQL in terms of data modeling?
Re: Building PlanetScale with PlanetScale
#19This looks quite compelling, but what about use cases where "serverless" is simply not viable. In some industries, you must control access to the server in order to stay compliant with regulations. At least for some of the data. Is there a plan to have a software-only release? Or did I just miss it.