Source: thenewstack.io
Serverless on Public Cloud: The Ultimate ShowdownCategory: Microsoft, Infrastructure, container
Getting a straight feature comparison is challenging, as the actual operational characteristics of each serverless platform can vary significantly — from how the serverless functions are invoked, to how they are billed. In this article, we’ll discuss the serverless offerings of each of the three major cloud service providers: Amazon Web Services, Google Cloud and Microsoft Azure.
For many companies, choosing AWS to drive their serverless functions means keeping all of their infrastructures in one place, as by some accounts AWS runs approximately 40% of the cloud market.
As with AWS, a number of triggers are available for Google Cloud Functions, from simple HTTP triggers to workflows driven by Cloud Scheduler and Cloud Tasks.
This was after a long beta period, during which Microsoft continued to enhance the ties between Azure Functions and the rest of the Microsoft Azure platform.
For many companies, choosing AWS to drive their serverless functions means keeping all of their infrastructures in one place, as by some accounts AWS runs approximately 40% of the cloud market.
As with AWS, a number of triggers are available for Google Cloud Functions, from simple HTTP triggers to workflows driven by Cloud Scheduler and Cloud Tasks.
This was after a long beta period, during which Microsoft continued to enhance the ties between Azure Functions and the rest of the Microsoft Azure platform.
Related Articles
Community Partners
DevOps Careers