{"id":3280,"date":"2017-11-20T00:00:00","date_gmt":"2017-11-20T00:00:00","guid":{"rendered":"http:\/\/otava.test\/what-is-function-as-a-service-faas\/"},"modified":"2017-11-20T00:00:00","modified_gmt":"2017-11-20T00:00:00","slug":"what-is-function-as-a-service-faas","status":"publish","type":"post","link":"https:\/\/www.otava.com\/blog\/what-is-function-as-a-service-faas\/","title":{"rendered":"What is Function as a Service (FaaS)?"},"content":{"rendered":"

\"Function<\/p>\n

We talked a little about serverless computing<\/a>, and its basic building blocks known as functions<\/b>\u00a0in an earlier post. <\/b>Functions have their own service, conveniently called Function as a Service (FaaS). What are functions, and how do they relate to serverless computing?<\/p>\n

FaaS is the concept of serverless computing using serverless architectures. It especially affects software developers, who can leverage this concept to deploy an individual \u201cfunction\u201d, action, or piece of business logic. These functions are expected to start within milliseconds and process individual requests before ending. The developer doesn’t have to worry about writing code to fit a given infrastructure–all he has to do is write code, and upload it to a serverless platform such as Azure Functions or AWS Lambda, which takes care of the rest.<\/p>\n

Like serverless computing, FaaS has its drawbacks. It’s best for event-based architectures (e.g., adding a file to blog storage, which would trigger a function to complete a task like sending an email or updating a database) such as Azure Event Grid (link), Microsoft’s serverless event-based management service. It’s not good for large applications, where containers (link) might be a better fit.<\/p>\n

The principles<\/a> of FaaS include:<\/p>\n