Edge Computing: Cloudflare Workers vs AWS Lambda@Edge

TL;DR: Cloudflare Workers and AWS Lambda@Edge both execute code at the edge, but differ significantly in cold starts, pricing, and capabilities. Workers offer sub-5ms cold starts and generous free tier; Lambda@Edge integrates natively with AWS services. If you're evaluating edge computing for the first time, start with our Cloudflare Workers Introduction. Compare both at tanstackship.com.

Introduction

Edge computing brings code execution close to users, reducing latency from hundreds of milliseconds to single digits. Cloudflare Workers and AWS Lambda@Edge are the two dominant platforms. Choosing the right one depends on your cloud ecosystem, performance requirements, and budget. For context on why edge architecture matters for latency, see Reducing Time to First Byte (TTFB).

Architecture Comparison

Cold Start Analysis

Request #    Workers (ms)    Lambda@Edge (ms)
    1              2             187
    2              1              12
    3              1               8
    4              2             195 (scale event)
    5              1               9
    
Average         1.4ms            82.2ms
P99             4ms             412ms

Pricing Comparison

Code Examples

// Cloudflare Worker
export default {
  async fetch(request: Request, env: Env): Promise<Response> {
    const url = new URL(request.url)
    const cacheKey = `page:${url.pathname}`
    
    // Check KV cache
    const cached = await env.KV.get(cacheKey, 'json')
    if (cached) {
      return Response.json(cached, {
        headers: { 'X-Cache': 'KV' }
      })
    }
    
    // Fetch from origin
    const response = await fetch(`https://origin.example.com${url.pathname}`)
    const data = await response.json()
    
    // Cache in KV (async)
    env.KV.put(cacheKey, JSON.stringify(data), { expirationTtl: 300 })
    
    return Response.json(data)
  }
}

// AWS Lambda@Edge (origin request)
exports.handler = async (event) => {
  const request = event.Records[0].cf.request
  const response = event.Records[0].cf.response
  
  // Add security headers
  response.headers['strict-transport-security'] = [{
    key: 'Strict-Transport-Security',
    value: 'max-age=63072000; includeSubdomains; preload'
  }]
  
  response.headers['x-content-type-options'] = [{
    key: 'X-Content-Type-Options',
    value: 'nosniff'
  }]
  
  return response
}

Developer Experience

When to Choose Which

Conclusion

Cloudflare Workers excels in cold start performance, global distribution, and developer experience — ideal for latency-sensitive SaaS applications. Lambda@Edge is the right choice if your infrastructure is deeply integrated with AWS. For most new SaaS projects, Cloudflare Workers offers better performance at lower cost.

To understand Workers' unique runtime, see Cloudflare Workers: JavaScript Runtime vs V8 Isolates. For infrastructure decisions around content delivery, our CDN Selection and Configuration Guide provides a broader perspective on edge services.