Get Started with Azure Functions
Serverless architecture also called as Function-as-a-Service is an event-triggered computing model. “Serverless” doesn’t mean there are no servers. They are abstracted so the developers are free from having to manage servers and enable them to focus on writing code. Serverless code is event-driven and the trigger can be anything from an HTTP request to a Blob. I will talk about Microsoft Azure’s serverless offering Azure Functions in this post. Let’s get started with Azure Functions.
Some of you may have a question. Isn’t the same problem PaaS also solves. Not worrying about the infrastructure, servers, and others. You are right. PaaS does solve the issues, but there are some major differences between these two. PaaS provides more control over the deployment environment compare to serverless. Scaling is automatic in serverless but in PaaS, you have to configure it manually. In PaaS, the application takes time to spin up while serverless executes only when invoked.
I am going to create an Azure Function app that generates a GUID and returns to the user on an HTTP request.
Please visit the following link for more details.