| I absolutely like managing servers. It makes sure I am fully aware where my data is at what time, and what is handling it. in a European world with GDPR that became a lot more important. At the same time this has been a big factor in recent data leaks. Those leaks happened mainly because implementation issues, but those organisations didn't choose to make their data available in unsecured S3 buckets. It was able to happen because they didn't have enough visibility. There's also many reasons given that don't really make sense. > Your containers are cattle, not pets. If your container crashes, a new one is automatically fired up. If my container crashes, I want to find out why so I can prevent it from happening again. One of the issues with these serverless technologies is that they make this kind of debugging harder. I don't want code to randomly crash and just getting restarted to be the solution. It means there is something wrong. To be fair he does mention this later on in the article. > Serverless functions force you to write your code in a stateless way So what. If I want to have my own server I can also do it stateless if that makes sense to me. Being forced in a direction is not a positive. I think the scaling is very interesting. But this is not something that's required for many applications. It doesn't mean everything should be serverless. It just means there's a good option to choose from for usecases that can really benefit from it. Pushing serverless for everything is like putting blockchain into everything because it's a buzzword right now. |