에지의 서버리스 함수

Serverless functions are small pieces of code that run in response to events, without you managing servers. Edge functions take this a step further by deploying and running this code at network edge locations, geographically closer to your users.

This minimizes the distance data needs to travel, leading to faster interactions.

Running serverless functions at the edge dramatically reduces latency – the delay before a transfer of data begins. Instead of requests traveling to a central cloud region, they hit an edge location nearby.

This means faster responses, a smoother user experience, and reduced load on your origin servers.

Edge functions are typically triggered by events, most commonly HTTP requests. When a user makes a request, the nearest edge location receives it, executes your function, and returns a response.

• They are deployed globally across a Content Delivery Network (CDN) or similar edge network.
• They wake up instantly on demand to handle requests.
• You only pay for actual execution time, making them cost-efficient.

Edge functions are often written in JavaScript (or WebAssembly) and intercept requests or responses. Here's a conceptual example of a function that modifies a response header before sending it to the user:

Edge functions can inspect incoming requests (like user's location, device type, or cookies) and dynamically alter the content served. This happens before the request even reaches your main application server.

• Show different product recommendations.
• Display localized promotions or currencies.
• Redirect users to mobile-optimized pages.

Before requests hit your backend APIs, edge functions can perform crucial tasks, acting like a lightweight API gateway:

• Authentication & Authorization: Verify tokens or API keys.
• Rate Limiting: Prevent abuse by blocking excessive requests.
• URL Rewriting: Clean up URLs or route requests to different origins.
• Header Manipulation: Add or remove HTTP headers for security or tracing.

While both are serverless, edge functions are distinct from traditional cloud-based serverless (like AWS Lambda in a single region):

• Proximity: Edge functions run much closer to the user.
• Execution Environment: Often lighter-weight, optimized for speed.
• Triggering: Primarily HTTP/CDN events for edge, broader event sources for cloud.
• State: Edge functions are typically stateless by design.

Deploying serverless functions at the edge offers several compelling advantages:

• Reduced Latency: Faster user experiences globally.
• Lower Origin Load: Less traffic hitting your main servers.
• Enhanced Security: Filter malicious requests and apply security rules closer to the source.
• Improved Reliability: Distributed execution reduces single points of failure.
• Cost Efficiency: Pay only for execution, often cheaper for high-volume, low-compute tasks.

While powerful, edge functions have some considerations:

• Cold Starts: Initial execution can be slightly slower if not recently used (though often highly optimized).
• Statelessness: Managing user sessions or persistent data typically requires external services.
• Debugging: Distributed nature can make debugging more complex across many locations.
• Resource Limits: Shorter execution times and less memory than traditional cloud functions.

Which of the following are primary benefits of running serverless functions at the edge?

In this lesson, we explored serverless functions at the edge. We learned that they bring compute logic closer to users, offering significant benefits like reduced latency, lower origin server load, and enhanced personalization.

We also saw how they can be used for API gateway logic and understood their distinct advantages compared to traditional cloud serverless, along with some key considerations.