(no title)
auspex | 3 years ago
Serverless functions are great if you have a lot of small services that need to be "on standby at all times".
For example if you have 5000 separate services, it doesn't makes sense to have them all running all the time if 4,000 of them have very low traffic. So one of the main benefits is that you get the ability to "increase your library of services at a very low cost". Serverless also really shines with quick stateless actions.
However, converting an app to all serverless is a huge task and for most apps it doesn't make sense.
Two major drawbacks:
1) You're bound to only the language versions that are currently supported.
2) You're writing code specifically for the platform so without a heavy lift you're "locked in"
If the goal is to go serverless and get rid of the server management, I'd suggest looking into containerizing your existing apps and deploying on a "serverless" managed service like Fargate (or your favorite cloud provider's equivalent). This approach is also lets you go to a different cloud provider if you want... or even move back to your own datacenter with no code changes.
No comments yet.