I've decided to go Serverless when implementing a search functionality for my personal blog recently [1]. Reasons were security (no need to maintain a custom b

I've decided to go Serverless when implementing a search functionality for my personal blog recently [1]. Reasons were security (no need to maintain a custom box, install patches etc.) and cost. With the low request volume I expect for this API, Serverless is essentially for free or a few cents. It definitely wouldn't be cheaper for a constant significant load in which case running your own VM will be more cost-efficient. Serverless doesn't necessarily mean you can't use your traditional frameworks. E.g. I'm using JAX-RS (I'm a Java guy) for my search. This app is compiled into a native binary via Quarkus and GraalVM, so it starts up fast enough, also cold starts are no problem. Re vendor lock-in mentioned by other commenters, that's not necessarily true either. My app is portable, I can deploy it to Lambda (via the API Gateway proxy integration) or as a regular app e.g. in a container running everywhere. Also "serverless" doesn't imply Faas (functions); there's container-based serverless like Knative, where you deploy your services as a container bound to some HTTP port. I.e. no lock-in at all, and you still have the benefits of serverless like auto-scaling, A/B testing, per-per-request etc. [1] https://www.morling.dev/blog/how-i-built-a-serverless-search-for-my-blog/ https://www.morling.dev/blog/how-i-built-a-serverless-search...