==== Advantages of Serverless:
- Stability: You're only deploying parts of the backend at a time, which reduces chances of breaking the entire application.
- Scaling: You can have parts of your backend scale with use, rather than scaling the entire monolithic backend.
- Cost: Serverless is surprisingly cheap these days, compared to hosting a full PHP/Python server.
==== Disadvantages of Serverless:
- Complexity: Serverless a.k.a "micro services", are basically tiny servers. This adds a bit of complexity, with authentication, latency etc. As it's not a single monolithic server anymore.
Many other drawbacks are inherently related to the added complexity.
In my experience it's worth trying, but if you're a one-man team then; a monolithic server is much easier/faster to deploy, test, and iterate on.
- Stability: You're only deploying parts of the backend at a time, which reduces chances of breaking the entire application.
- Scaling: You can have parts of your backend scale with use, rather than scaling the entire monolithic backend.
- Cost: Serverless is surprisingly cheap these days, compared to hosting a full PHP/Python server.
==== Disadvantages of Serverless:
- Complexity: Serverless a.k.a "micro services", are basically tiny servers. This adds a bit of complexity, with authentication, latency etc. As it's not a single monolithic server anymore.
Many other drawbacks are inherently related to the added complexity.
In my experience it's worth trying, but if you're a one-man team then; a monolithic server is much easier/faster to deploy, test, and iterate on.