As a software architect, I hate serverless. Not because it doesn't work, but because it forces design constraints that cripple your application. Here's why always-on servers matter.
Article exactly describes how I feel about next.js -ers.
So far none of them was able to explain to me why lack of connection pooling is A good thing. I doubt they even know what that is. If you build a website in server less - you might as well use php because it will beat node.js in raw speed on those conditions and you are handicapping it similarly.
And there it is. The reason for the whole article.
Article exactly describes how I feel about next.js -ers.
So far none of them was able to explain to me why lack of connection pooling is A good thing. I doubt they even know what that is. If you build a website in server less - you might as well use php because it will beat node.js in raw speed on those conditions and you are handicapping it similarly.