In the previous sections, we touched upon the basics of the serverless paradigm and saw how systems in production evolved to arrive at this point.
To recap, the serverless architecture started as Function as a Service, but has grown to be much more than just ephemeral computational units.
Serverless abstracts away the humdrum but critical (scalability, maintenance, and so on) and functional but standard (email, notifications, logging, and so on) pieces of your system, into a flexible offering that can be consumed on demand. This is like a case of build versus buy, where a decision to buy is made, but at a fraction of the upfront cost.
