# serverless architecture Serverless architecture is an application architecture in which developers build and run applications without managing physical or virtual servers, while the cloud provider manages infrastructure, scaling, and resource allocation. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The Original Serverless Architecture is Still Here DevFeed: [The Original Serverless Architecture is Still Here]() Original publisher: [Read original article]() Author: Khan Academy Published: 2018-05-31T22:00:00Z Content type: opinion Language: en Sources: [Khan Academy]() Topics: [serverless architecture](), [Kubernetes](), [Orchestration](), [Docker](), [Cloud](), [Firebase](), [DynamoDB]() Tags: [amazon](), [cloud](), [containers](), [docker](), [dynamodb](), [engineering](), [firebase](), [infrastructure](), [kubernetes](), [news](), [orchestration](), [serverless](), [serverless-architecture]() ### AI overview This commentary compares Kubernetes-based architectures with serverless approaches. It explains that Kubernetes offers flexibility through containers, Helm, ingress controllers, monitoring tools, and service meshes, but requires substantial configuration and maintenance. Serverless platforms such as Firebase and Amazon Lambda abstract away server infrastructure so developers can focus on applications and stateless functions. ### Source excerpt By Kevin Dangoor This month, my colleague Dave Rosile and I went to GlueCon 2018 in sunny Denver, ... Read more ## Firestore adds generally available pipeline operations with full-text search, JOINs, geospatial queries, and data manipulation DevFeed: [Firestore adds generally available pipeline operations with full-text search, JOINs, geospatial queries, and data manipulation]() Original publisher: [Read original article]() Author: Morgan Chen; Minh Nguyen Published: 2026-04-27T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Firestore](), [NoSQL](), [Database](), [Serverless](), [serverless architecture]() Tags: [database](), [firebase](), [firestore](), [full-text-search](), [geo-queries](), [geospatial](), [javascript](), [nosql](), [real-time](), [serverless](), [serverless-architecture]() ### AI overview Firestore pipeline operations reached general availability on the enterprise edition, adding full-text search, geospatial queries, JOIN capabilities through subqueries, and data manipulation while retaining Firestore's NoSQL and serverless features. ### Source excerpt With support for full-text search, joins, and geospatial queries, Firestore is ready to meet all of your app's querying needs. ## Making a Business Case for an Event-Driven Architecture DevFeed: [Making a Business Case for an Event-Driven Architecture]() Original publisher: [Read original article]() Author: Michael Stack Published: 2023-07-13T00:00:00Z Content type: article Language: en Sources: [Encore Updates]() Topics: [event driven](), [Architecture & Design](), [Scalability](), [serverless architecture](), [Cloud]() Tags: [architecture](), [cloud](), [event-driven](), [real-time](), [scalability](), [serverless]() ### AI overview This article examines whether an event-driven architecture is appropriate for a business, covering its costs, maintenance requirements, integration with existing systems, and potential benefits. It discusses real-time processing, improved data accuracy, independent scaling, cloud-based serverless deployment, and timely user updates. ### Source excerpt Taking the first steps towards an EDA ## Square Payroll's Migration from a Monolith to Microservices DevFeed: [Square Payroll's Migration from a Monolith to Microservices]() Original publisher: [Read original article]() Author: Harold Sultan Published: 2022-10-12T04:00:00Z Content type: article Language: en Sources: [Square Corner Blog](), [Square Corner Blog RSS Feed]() Topics: [Microservices](), [migration](), [Amazon Web Services](), [Serverless](), [serverless architecture](), [Architecture & Design](), [Ruby](), [MySQL](), [Sidekiq]() Tags: [architecture](), [aws](), [engineering](), [microservices](), [migration](), [mysql](), [ruby](), [serverless](), [serverless-architecture](), [sidekiq]() ### AI overview Square describes an early step in migrating Square Payroll from a Ruby monolith backed by MySQL to a more scalable architecture. The article focuses on redesigning its tax filing system with AWS serverless architecture and using a Step Function to reduce code complexity and improve transparency. ### Source excerpt Scaling with AWS serverless architecture ## A Guide to Serverless Architecture DevFeed: [A Guide to Serverless Architecture]() Original publisher: [Read original article]() Author: Gareth McCumskey Published: 2022-05-17T00:00:00Z Content type: tutorial Language: en Sources: [Serverless Blog]() Topics: [serverless architecture](), [Serverless]() Tags: [3](), [architecture](), [article](), [aws](), [aws-lambda](), [cloud-computing](), [engineering](), [examples](), [faas](), [function-as-a-service](), [guide](), [infrastructure-as-code](), [learn](), [serverless](), [serverless-architecture](), [serverless-framework]() ### AI overview A guide explaining serverless architecture, three benefits of using it, and examples of how it is used. ### Source excerpt In this article learn what serverless architecture is, 3 benefits to using it, and see examples of how it's being used. ## Maintaining WebSocket Connections with GraphQL Subscriptions in a Serverless Environment DevFeed: [Maintaining WebSocket Connections with GraphQL Subscriptions in a Serverless Environment]() Original publisher: [Read original article]() Author: Shaila Kavrakova Published: 2021-03-31T14:49:04Z Content type: tutorial Language: en Sources: [RBI Tech]() Topics: [WebSocket](), [Serverless](), [serverless architecture](), [AWS Lambda](), [Amazon API Gateway](), [GraphQL]() Tags: [amazon-api-gateway](), [apollo](), [aws](), [aws-lambda](), [graphql](), [serverless](), [serverless-architecture](), [web-applications](), [websocket]() ### AI overview This article explains how WebSockets provide persistent, bidirectional communication for real-time web applications and examines the challenge of using them with event-driven serverless architecture. It introduces AWS Lambda and Amazon API Gateway as relevant components. ### Source excerpt Maintaining a sustained connection with WebSockets and GraphQL Subscriptions in a serverless environment Photo by https://unsplash.com/@plhnk As modern technology and web applications advance, the expectation of immediate feedback and constant communication is apparent. We're accustomed to this phenomenon of instant gratification where we are fulfilled with very little or hardly any wait time at all. Just think about how we're able to receive certain packages with same day delivery. The world is at our finger tips. This continuous cause and effect cycle needs to be seamless, otherwise you run the risk of the end user becoming impatient or frustrated. WebSockets One way to achieve real time updates is through a persistent connection. This is where WebSockets come into play. A WebSocket is a transport protocol which provides a bi-directional communication channel between client and server via a sustained connection. Typical HTTP/S requests are uni-directional meaning only allowing for requests to be sent from client to server. WebSockets render polling (aka constant request/response cycles) obsolete. Once a connection is established, connection channels persist and are re-used to exchange messages back-and-forth. Some popular use cases for WebSockets are real time applications such as chat apps and multiplayer games. The server is able to push new updates without the need for frequent requests from the client. Instant gratification! Serverless Serverless architecture enables us to build and run our applications without the infrastructure overhead. When it comes to serverless, it's helpful to keep in mind that it is strictly event based. Events trigger other events. In the case of AWS Lambda, it will run our code on an as-needed basis in response to a given event. Due to this, it is not a long running process and is very transactional in nature. This brings me to the question at hand, what if we wanted to take advantage of WebSockets but with all the advantages of serv ## Lessons Learned From Sending Millions of Serverless Webhooks DevFeed: [Lessons Learned From Sending Millions of Serverless Webhooks]() Original publisher: [Read original article]() Author: Rocky Warren Published: 2019-05-27T00:00:00Z Content type: article Language: en Sources: [Serverless Blog]() Topics: [serverless architecture](), [Serverless]() Tags: [architecture](), [aws](), [aws-lambda](), [cloud-computing](), [cost](), [customers](), [faas](), [function-as-a-service](), [infrastructure-as-code](), [serverless](), [serverless-architecture](), [serverless-framework](), [webhooks]() ### AI overview The article discusses lessons from using a serverless architecture to send millions of Dwolla's webhooks faster and at a lower cost. ### Source excerpt Using a serverless architecture to send Dwolla's webhooks faster and at a lower cost. ## MoonMail's Serverless Architecture for an Open Source Email Marketing App DevFeed: [MoonMail's Serverless Architecture for an Open Source Email Marketing App]() Original publisher: [Read original article]() Author: Carlos Castellanos Published: 2017-01-05T00:00:00Z Content type: article Language: en Sources: [Serverless Blog]() Topics: [Serverless](), [serverless architecture](), [App](), [Open Source]() Tags: [app](), [architecture](), [aws](), [aws-lambda](), [cloud-computing](), [customers](), [email](), [faas](), [function-as-a-service](), [guest-post](), [infrastructure-as-code](), [marketing](), [open-source](), [serverless](), [serverless-architecture](), [serverless-framework]() ### AI overview A guest post describes how MoonMail designed a serverless architecture for its open source email marketing app. ### Source excerpt Get a sneak peek at how MoonMail designed their serverless architecture for an infinitely scalable open source email marketing app in this guest post. ## Serverless Architecture and Functions as a Service DevFeed: [Serverless Architecture and Functions as a Service]() Original publisher: [Read original article]() Author: umer Published: 2016-06-25T00:00:00Z Content type: article Language: en Sources: [Code Ahoy - Articles]() Topics: [Serverless](), [serverless architecture](), [Back end](), [AWS Lambda](), [azure functions](), [Cloud Functions](), [Google Cloud Platform (GCP)]() Tags: [architecture](), [aws](), [aws-lambda](), [azure](), [azure-functions](), [backend](), [cloud-functions](), [event-driven](), [google](), [google-cloud](), [serverless](), [serverless-architecture]() ### 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