Hm 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?

Tangentially related, is this book worth the hype? I don't read a lot of genre fiction, but don't like to miss out on the exceptional (just finished and loved Flowers for Algernon, as an example).

Edit: Sounds like an enjoyable, low commitment book. Will give it a try, thanks for the feedback.

I don’t get it. Sending a query to a remote server is going to be much slower than sending the query to local database. When has Postgres not been enough on its own?

I agree with the overall sentiment of this post.

I’ve learned (sometimes the hard way!) that every design choice comes with real trade-offs. There’s no magic database architecture that optimizes every dimension (e.g., scalability, performance, ease-of-use) simultaneously.

Social media often pushes us into oversimplified "winner vs. loser" narratives, but this hides the actual complexity of building great infrastructure.

Recognizing and respecting these differences makes us smarter engineers, better community members, and frankly, just more enjoyable people to chat with.

PS Thank you for helping me add a new book to my list :-)

tldr; Supabase. XD

The discussion centers on speed and scalability. I recently used Neon in a project mainly because it was easy to setup.