# Serverless Architecture and Functions as a Service

DevFeed: [Serverless Architecture and Functions as a Service](<https://devfeed.tech/articles/what-is-serverless-architecture-aws-lambda-features-2020-24952.md>)

Original publisher: [Read original article](<https://codeahoy.com/2016/06/25/serverless-architectures-lets-ditch-the-servers/>)

Author: umer

Published: 2016-06-25T00:00:00Z

Content type: article

Language: en

Sources: [Code Ahoy - Articles](<https://devfeed.tech/sources/code-ahoy-articles.md>)

Topics: [Serverless](<https://devfeed.tech/topics/serverless.md>), [serverless architecture](<https://devfeed.tech/topics/serverless-architecture.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [AWS Lambda](<https://devfeed.tech/topics/aws-lambda.md>), [azure functions](<https://devfeed.tech/topics/azure-functions.md>), [Cloud Functions](<https://devfeed.tech/topics/cloud-functions.md>), [Google Cloud Platform (GCP)](<https://devfeed.tech/topics/google-cloud.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [azure](<https://devfeed.tech/tags/azure.md>), [azure-functions](<https://devfeed.tech/tags/azure-functions.md>), [backend](<https://devfeed.tech/tags/backend.md>), [cloud-functions](<https://devfeed.tech/tags/cloud-functions.md>), [event-driven](<https://devfeed.tech/tags/event-driven.md>), [google](<https://devfeed.tech/tags/google.md>), [google-cloud](<https://devfeed.tech/tags/google-cloud.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [serverless-architecture](<https://devfeed.tech/tags/serverless-architecture.md>)

## AI overview

This article explains serverless architecture through the Functions as a Service model. It describes how cloud providers manage infrastructure and execute code in response to requests or events, and how applications can be designed as collections of single-purpose backend functions.

## Source excerpt

Serverless is the new buzzword that is quickly gaining momentum and attention. The concept is to be able to run server-side code without worrying about the messy details of provisioning and setting up servers, disk drives and other resources. You write code, upload it and -- voilà! -- it starts running. All the complications of managing the infrastructure, provisioning servers, auto-scaling, installing languages and frameworks are eliminated and hidden away by the cloud provider (AWS, Azure, Google Cloud). The cloud provider takes care of allocating and managing the resources, invoking the code in response to a request, providing it the context and input information it needs to do its job and return the result to the client. By focusing less time on managing scaling and availability, software developers are increasingly using serverless architectures for more advanced workloads. Functions as a Service There is no clear view or consensus on what serverless is; for many people, it means writing your code as function and giving it to cloud providers for execution. This is referred to as Functions as a Service** or *FaaS. This view of serverless is the main focus of this article. All major cloud vendors provide FaaS: AWS Lambda on AWS. The most popular implementation of FaaS. Azure Functions on Microsoft Azure Cloud Functions on Google Cloud Going serverless requires a different approach to application design. The backend service is broken down into stand-alone functions that perform a single task in response to a user action or event. In serverless architectures, the backend is composed of thin, single-purpose functions that are event driven. The business logic shifts from the backend to the client e.g. mobile app. It becomes the main orchestrator, calling various functions to perform some action for the user when needed. For example, running in serverless architecture, a photo-sharing app like Instagram might call one function to upload image to the server followed by a