Serverless computing is an exciting aspect of public cloud computing: You no longer have to provision virtual servers in the cloud; that’s done automatically to meet the exact needs of your application.Although the value of serverless computing is not in dispute, it’s my job to find potential downsides in new technologies so that my clients—and you—can avoid them.
In the case of serverless computing, we may find that cloud architecture as a discipline suffers. Here’s why.[ A developer’s guide: Get started with serverless computing. | Microsoft Azure Functions locks in on serverless computing. | Build ’em now! 5 uses for serverless frameworks. ]
When building applications for server-oriented architectures (where the virtual servers need to be provisioned, including storage and compute), you have built-in policies around the use of resources, including the virtual server itself.

After all, you have to provision servers before the workloads can access them.

That means you’re well aware that they’re there, that they cost money, and that they’re configured for your workloads.To read this article in full or to leave a comment, please click here

Leave a Reply