Flask and PostgreSQL in 5 minutes with Neon Database

There are plenty of opinionated Python frameworks, you just seem to dislike ones that aren't.

This is also showcasing the ease of setup of Neon, mostly. Previous announcement here: https://news.ycombinator.com/item?id=31536827

Flask because it's literally anything that serves an API easily.

There is something a little cheap about these kinds of blog posts, I certainly agree, but you seem to have a lot of pent-up anger for it.

Strongly disagree with the downvotes on this post.

The phenomenon you describe is real enough, but I’ve also seen teams lament their shortsightedness as they fight with the limitations of opinionated frameworks (cough… Django… cough). It’s extremely hard to choose the right tech. The best engineers I have worked with are just as good at minimizing the stakes of making the wrong decision as they are at making good ones.

Generally serverless means that you don't have to worry about the servers, not that it's not running on a server, of course it is. In this case, neon offers pretty good scalability that goes hand in hand with the usual serverless behaviour of having multiple instances of your code running in parallel, something which postgres alone is not very good at handling because of the "one process per connection" functionality. You'd need pgbouncer or RDS proxy on top of your postgres instance.