- No operating systems to choose, secure, patch, or manage.
- No servers to size, monitor, or scale.
- No risk to your cost by over-provisioning.
- No risk to your performance by under-provisioning.
There is no “one” way of doing serverless, Paul Johnson writes,
Serverless becomes about exposing individual functionality rather than a whole server.
Serverless is about saying exactly what needs doing when responding to an event, and increasingly ignoring what underlying technology is required.
But it’s also about removing the need to manage uptime, server maintenance, upgrades, security vulnerabilities etc. The only bit you need to be aware of is your code. That’s it.
Read more at Paul's blog...