starter.wiki中文

Infrastructure

Serverless Compute

Choose managed request or event execution by runtime compatibility, duration, concurrency, networking, state, and provider integration.

Recommendation

Choose the execution contract, not the serverless label.

Web-platform isolates, cloud event functions, and managed containers expose different packaging, compatibility, scaling, and ownership boundaries.12

For: Teams deploying bounded APIs, request handlers, event consumers, or stateless services without managing servers

Main trade-off

Managed scaling removes server operations while runtime limits, event semantics, quotas, networking, billing, and provider coupling move into the application boundary.12

Three managed compute contracts

Each route removes server management but keeps different runtime and platform constraints inside application design.

  1. Runtime compatibility

    Verify language version, libraries, native dependencies, APIs, packaging, startup, and container requirements.12

  2. Execution envelope

    Model duration, CPU, memory, concurrency, cold starts, request limits, and cancellation behavior.12

  3. State and networking

    Define external state, connections, private networking, egress, event sources, and regional requirements.34

  4. Platform ownership

    Account for IAM, observability, retries, deployment, quotas, adjacent services, and migration cost.12

Execution routes

Choose the smallest managed execution contract that fully supports the workload.

Web APIs and Cloudflare bindings fit

Evaluate Cloudflare Workers.

The isolate model supports distributed request and event execution with a low server-operations surface.

Verify: Unsupported Node.js behavior, persistent processes, arbitrary containers, or incompatible limits should move the route.12

AWS events and IAM define the system

Evaluate AWS Lambda Functions.

AWS event sources and service integrations can make the function boundary operationally coherent.

Verify: Persistent servers, incompatible duration or quota behavior, or unmodeled adjacent AWS costs should move the route.1234

A container contract is required without Kubernetes

Evaluate Google Cloud Run.

Managed request-driven services preserve broad container compatibility while avoiding cluster operations.

Verify: Kubernetes APIs, daemon behavior, or direct node and scheduler control require another container route.125

Boundary: This Task does not choose serverless databases, long-lived background workflows, schedulers, message brokers, or Kubernetes orchestration.

Serverless surfaces are not interchangeable

Packaging, lifecycle, state, and integration differences determine whether code can run correctly and economically.

Runtime
Isolate APIs, function runtimes, and containers accept different dependencies and server assumptions.12
Scaling unit
Requests, function invocations, and container instances create different concurrency and cold-start behavior.5
Integration
Bindings, event sources, IAM, networking, and service graphs create provider-specific architectures.34
Billing
Invocation, duration, CPU, memory, instance, networking, and adjacent-service charges must be modeled.12

Official resources

Use the primary documentation to verify runtime behavior, operating limits, service boundaries, and current commercial terms.

DocumentationAWS Lambda quotas

Sources

Official documentation supporting the routes and decision boundaries on this page.

  1. 1
    Cloudflare Workers documentation

    Cloudflare · Accessed Official

  2. 2
    Cloudflare Workers limits

    Cloudflare · Accessed Official

  3. 3
    AWS Lambda developer guide

    Amazon Web Services · Accessed Official

  4. 4
    AWS Lambda quotas

    Amazon Web Services · Accessed Official

  5. 5
    Google Cloud Run overview

    Google Cloud · Accessed Official