Serverless vs. Traditional Hosting
Hosting a web application involves choosing the right infrastructure to meet your application's needs...
For further actions, you may consider blocking this person and/or reporting abuse
What are some real-world examples where you’ve seen serverless hosting outperform traditional hosting?
We can use for reverse proxy, example ->Helps in Legacy transition to modern using strangler pattern
For Small Scale Bushinesses
Serverless, in my experience, is not about costs. It is about TTM, which is crucial for new products. It provides scalability, observability, and resilience out of the box. Any non-trivial system would require more than one machine. At a bare minimum, you need to run a database, backups, monitoring system, and your app code itself. The database is usually 2/3 VMs for replication and more for sharing. Another machine for storing logs, metrics and running monitoring dashboard. And a couple for your app code so you can perform maintenance without downtimes. Since you have more than one application server you might also need a load balancer. Serverless systems like AWS Amplify give you all of this out of the box. It allows you to start iterating right away, and then when the system is mature and the user load is predictable, optimize costs by migrating to traditional hosting.
P.S.: I'm not talking about more complex scenarios, where you need a message queue, object storage, analytics system, multiple types of databases, secrets vault, container registry, reverse proxy, API gateway, and many other things. However, serverless might be a better choice in this scenarios as well if it runs in a cloud that provides all the required services.
Costs == TTM 😉
image issue
Fixed btw thanks for the information
Serverless is a stateless runtime for small applications that needs fast term aren't it.
Thanks for this sweet and simple article
Thanks for the appreciation bro ❤️
Thank you, I liked the scenario breakdown & the pros and cons of each