Serverless edge: Bringing services right next to the end-user

• Author:
• Author name

  Quantumrun Foresight
• March 23, 2023

Insight summary

Since the late 2010s, serverless platform providers increasingly shifted to edge computing paradigms to manage latency (the time it takes for signals to reach devices) by giving some control back to the developer instead of the cloud service. Edge computing’s success is due in large part to the advancements and popularity of content distribution networks (CDNs) and global infrastructures.

Serverless edge context

Data that is located “on the edge” is typically stored in CDNs. These networks store data in a more localized data center closer to the user. While there is not yet a clear definition of serverless edge, the premise is that data will be increasingly distributed and more flexibly stored for the user. 

Edge functions are becoming more popular because serverless (or cloud-based services) have some limitations, like latency and observability. Even though serverless makes it reasonably easy to build and deploy cloud applications, edge computing tries to make them even better. The developer experience is enhanced by serverless since cloud providers handle the administration of computing resources. Although this method streamlines front-end development, it also restricts control and insight into system infrastructure, which may be addressed by edge computing.

The more work an edge server can handle, the less work the origin server has to do. In addition, the overall processing power of the network is many times greater than that of the origin server alone. As a result, it’s sensible to offload tasks to downstream edge functions and free up time on the origin server for specialized backend activity.

The most applicable modern-day example is Amazon Web Services (AWS)’s Lambda@Edge. Code is now run closer to the user, decreasing latency. Customers do not have to deal with infrastructure and are only charged for their computing time. 

Disruptive impact

A new wave of serverless is poised to benefit end-users and developers, unlike prior technologies. Serverless apps’ adaptable and decentralized nature makes them capable of being deployed in locations previously out of reach: the edge. Edge serverless enables serverless apps to be run on devices worldwide, giving all users the same experience no matter how close they are to the central cloud.

For example, cloud platform company Fastly Solutions’ Compute@Edge runs from 72 locations simultaneously, as near to end-users as possible. Edge serverless architectures allow for apps to be hosted locally while still providing the power of central cloud computing. The apps run on the firm’s edge cloud, so they’re responsive enough for a round-trip request for each keystroke. That type of interactivity is impossible to achieve with a central cloud structure.

Pay-per-use seems to be the emerging business model in the serverless edge space. In particular, Internet of Things (IoT) applications can have an unpredictable workload, which doesn’t work well with static provisioning. Static container provisioning charges users even when their application is idle. This mechanism can be a problem when the application has a lot of work to do. The only way to solve this problem is to add more capacity, but it may be expensive. In contrast,  the cost in serverless edge is based on actual triggered events, such as a dedicated resource and how many times a function is invoked. 

Implications of serverless edge

Wider implications of serverless edge may include: 

• Media and content-based companies being able to deliver content without buffering, and that can be stored in caches for faster loading.


• Program developers being able to test codes and applications quickly with every modification, leading to faster product launches. 


• As-a-service firms (e.g., server-as-a-service, product-as-a-service, software-as-a-service) providing better connectivity to their end-users, as well as better pricing options.


• Easy access to open-source components and tools that allow for faster creation of modules, systems, and applications.


• Real-time updates and instant access to data crucial to smart city technologies, such as traffic monitoring.

Questions to consider

• What are the other potential benefits of services closer to the user?


• If you are a software developer, how is serverless edge going to improve how you perform your tasks?