With a FaaS application this is completely transparent. with Heroku how many Dynos you want to run. With most PaaS’s you still need to think about scale, e.g. The key operational difference between FaaS and PaaS is scaling. Most PaaS applications are not geared towards bringing entire applications up and down for every request, whereas FaaS platforms do exactly this. Some consider FaaS as just another PaaS, but Mike Roberts, VP of Engineering at Intent Media, has another opinion: Few use the term nanoservice, most preferring microservice or even just service. When a “Create Account” event is triggered, the respective nanoservice is executed as a AWS Lambda function.
WHAT IS SERVERLESS ARCHITECTURE A PAAS CODE
For example, a microservice could be represented by the code needed to perform all CRUD operations on an account, while there is a nanoservice for each account operation: create, read, update, and delete. If a microservice is a process meant to address a relative small business capability, a nanoservice deals with a fraction of the respective capability. The serverless architecture goes well with nanoservices. Others include Google Cloud Functions, Microsoft Azure Functions, IBM OpenWhisk with an open source implementation, Iron.io, and Webtask. Some have called this type of functionality Function-as-a-Service (FaaS), which is Yet-Another-as-a-Service (YAssS), one of many that have appeared since cloud computing made its debut.Īmazon is not the only FaaS provider. And the execution is metered in units of 100 ms, the user being charged only for the resources consumed when the code is run. The containers used to run these functions are decommissioned as soon as the execution ends. The cloud provider takes care of finding a server where the code is to run, and to scale up when necessary.
![what is serverless architecture a paas what is serverless architecture a paas](https://www.skyalleys.com/wp-content/uploads/2018/12/OnPremise-vs-IaaS-PaaS-SaaS.jpg)
All that matters is to write the piece of code to be executed when a certain event takes place. One does not have to consider the server when using this paradigm. There is no perpetual process running on a server and waiting for HTTP requests or API calls, but an event mechanism that triggers the execution of a piece of code, usually just a function, on one of AWS’ servers. This service infrastructure was usually called Backend-as-a-Service (BaaS) or Mobile Backend-as-a-service (MBaaS).īut Amazon took the serverless paradigm to another level when they announced AWS Lambda back in 2014, introducing a new system architecture for applications running in the cloud. Not that there were no servers involved, but the back-end infrastructure was maintained by third party providers and the functionality needed was offered as services, covering databases, messaging, authentication, etc. Initially, serverless meant developers did not have to care for setting up and administering the servers running their back-end applications. This article discusses what serverless is, comparing it with PaaS and SPaaS, the benefits and costs of a serverless architecture and the need for a framework.