Interesting observation, but I think your article is heavily about running node.js on AWS’s serverless.

Personally, I use the latest ASP.Net core using AWS’s serverless and its great. The nuget packages are pre-bundled with the application and so there is no need to install anything in the lambda environment on startup — everything is ready for action.

Firstly all the API's are combined into one function, so there is no need for warming every function, there is only one warm per API per client app instance. I do the warming on a separate thread as the client app (which run on all platforms including mobile btw) is doing its initialisation — so by the time the user tries to login the API is already warm.

Secondly, I do agree that you have to design your code to deal with a stateless environment from the ground up to use serverless— but I would argue everyone should be doing this 2019 anyway — state is simply evil and has enough problems of its own. Even without serverless I wouldn’t use state at all.

In over 16 years of professional development, and 7 years before that, I have never encountered an environment I enjoy working in more than AWS’s serverless one.

I use Lambda for the API, Aurora Serverless for the DB, and API Gateway in front of it all to protect everything and to prevent dos attacks etc.

You do have to make all your decisions consciously for this environment, but I would argue that you always have to do that for all different types of environments — it's simply that you are more used to your old school environment.

Plus, if one uses ASP.Net Core you also get the benefit of sharing code between front-end and backend — as C# can be used everywhere nowadays.

I would encourage you to stick it out — just because its different doesn’t mean its worse — it just means you have to learn more and that's never a bad thing in our line of work