Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

PlanetScale – Database for Developers

planetscale.com

Post reply on HN
Print view View original

1–10 of 135 posts

Re: PlanetScale – Database for Developers

#2

Post by sorenbs »

I have been using the beta version of PlanetScale for a while, and it is extremely cool. It's using the mature technology that powers Youtube to provide a developer experience for databases similar to what Vercel and Netlify provide for hosting: It will give you a database branch for each Git branch and help you manage the workflows around it.

And it is the first truly serverless relational database offering that I am aware of. The cost scale to 0, so it is perfect for small projects, but that same instance will scale to support massive load when you need it.

Re: PlanetScale – Database for Developers

#3

Post by cfors »

> Developers want the durability, stability, and scalability of a SQL database but do not want to be constrained by managing a schema. It has been our goal to give both, not compromising on the power of your datastore but making changes feel as easy as deploying code.

So is this a wrapper around managing Schemas powered by Vitesse? (Btw, had to go to your github to figure that out)

If you want to be the database for developers you should know that developers do care about how you do this scaling.

Re: PlanetScale – Database for Developers

#6

Post by Rauchg »

From the Vercel point of view, this promises to answer one of the most frequent, interesting, and technically challenging questions since we first launched our "immutable deploys".

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.

Re: PlanetScale – Database for Developers

#7

Post by adamfeldman »

Rauchg wrote: post #6

From the Vercel point of view, this promises to answer one of the most frequent, interesting, and technically challenging questions since we first launched our "immutable deploys". 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.

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
Post reply on HN