FaaS is a serverless backend service allowing developers to write modular pieces of code on the fly that can be executed in response to certain events.
After reading this article you will be able to:
Copy article link
Function-as-a-Service (FaaS) is a serverless way to execute modular pieces of code on the edge. FaaS lets developers write and update a piece of code on the fly, which can then be executed in response to an event, such as a user clicking on an element in a web application. This makes it easy to scale code and is a cost-efficient way to implement microservices.
If a web application were a work of visual art, using microservice architecture would be like making the art out of a collection of mosaic tiles. The artist can easily add, replace, and repair one tile at a time. Monolithic architecture would be like painting the entire work on a single piece of canvas.
This approach of building an application out of a set of modular components is known as microservice architecture. Dividing an application into microservices is appealing to developers because it means they can create and modify small pieces of code which can be easily implemented into their codebases. This is in contrast to monolithic architecture, in which all the code is interwoven into one large system. With large monolithic systems, even a minor changes to the application requires a hefty deploy process. FaaS eliminates this deploy complexity.
Using serverless code like FaaS, web developers can focus on writing application code, while the serverless provider takes care of server allocation and backend services.
With FaaS, developers can spend more time writing application logic and less time worrying about servers and deploys. This typically means a much faster development turnaround.
Since FaaS code is inherently scalable, developers don’t have to worry about creating contingencies for high traffic or heavy use. The serverless provider will handle all of the scaling concerns.
Unlike traditional cloud providers, serverless FaaS providers do not charge their clients for idle computation time. Because of this, clients only pay for as much computation time as they use, and do not need to waste money over-provisioning cloud resources.
Having a third party manage part of the infrastructure makes it tough to understand the whole system and adds debugging challenges.
It can be very difficult to incorporate FaaS code into a local testing environment, making thorough testing of an application a more intensive task.
Developers must create a relationship with a serverless provider in order to enable FaaS functionality for a web application. Since FaaS integration means some application code will be delivered from the edge, availability and geographical distribution of edge servers is an important consideration. A user in Italy accessing a site that relies on FaaS edge code served from an overloaded data center in Brazil will encounter the kind of delay that leads to high bounce rates. Cloudflare Workers is a FaaS solution that takes advantage of Cloudflare’s global network with data centers in over 285 cities, making it a popular choice.
Learning Center Navigation