Simply put, serverless systems remove you from having to deal with infrastructure issues, such as storage and compute server provisioning or operations.
Indeed, many refer to serverless as “no-ops,” but it’s really “reduced-ops,” or as my friend Mike Kavis likes to say, “some-ops.” Clearly the objective is to increase simplicity and make building and deploying net-new cloud-based serverless applications much more productive and agile.
But serverless is not always a good idea. Indeed, it seems to be a forced fit a good deal of the time, causing more error than trial.
