alt Hacker NewsHm I feel like I jumped into the middle of something and don't understand the conclusion.
What's the beef between PlanetScale and Neon? Benchmarking, uptime, vibe coding?
The quote at the end doesn't really help me. Which one is good for what?
Replies
Long story short, I didn't want to make that analysis/distinction because it would miss the point.
They excel in their respective areas based on the architectural decisions they've made for the use cases they wanted to optimize for.
PlanetScale, with their latest Metal introduction, optimized for super low latency (they act like they've reinvented the wheel, lol), but they clearly have something in mind going in this direction.
Neon offers many managed features for serverless PostgreSQL that were missing in the market, like instant branching, and with auto-scaling, you may perform better with variable workloads. From their perspective, they wanted to serve other use cases.
There's no reason to always compare apples to oranges, and no reason to hate one another when everyone is pushing the managed database industry forward.
Edelman PR
To make it shorter than OP's reply, from my understanding of the offerings:
- PlanetScale for predictable load. You pick a config (CPU, memory) and if you don't have traffic it sits idle, and if you have traffic it's limited by the config you picked.
- Neon for scalability. You pay for compute hours, so if your traffic is spikey (e.g. concert ticket sales), you don't pay for idle resources during low traffic, and get all the compute you need during high traffic.