Serverless Is the Ultimate End Game

I think it really depends on the kind of app you're building, right? I think serverless is very advantageous for certain workloads. And for other workloads, it's a terrible, terrible, terrible idea. For instance, if you have an application that is all like a quote unquote, always on state, right? Like you don't need to manage state completely outside the application somewhere else and add even more latency. So these are things that you need some service that isn't going to give you some cold start problem. It has a little bit of warm-up time, so you need to be tolerant to spikes in traffic. Sometimes in probably in most cases, not at