starter.wikiSearch⌘K

Developer Workflow

Local Cloud Emulation

Choose local cloud-service emulation by provider scope, behavioral fidelity, test purpose, and lifecycle ownership.

Recommendation

Match the emulator to the provider and behavior under test.

Use provider-specific local tooling deliberately and keep a real-service verification stage for behavior the emulator cannot prove.12

For: Development teams testing applications that depend on AWS, Firebase, or Supabase services outside shared remote environments

Main trade-off

Local emulation improves speed, isolation, and offline workflows while introducing fidelity gaps, image and version drift, test-data lifecycle, local resource, licensing, and false-confidence risk.1234

Provider-specific emulation routes

AWS breadth, AWS serverless templates, Firebase services, and a local Supabase stack have different fidelity and lifecycle boundaries.

  1. Provider and service scope

    List every service API, event, IAM rule, network path, managed feature, extension, and version the application relies on.13

  2. Test purpose

    Separate fast developer feedback, deterministic integration tests, offline work, CI isolation, and production-parity verification.12

  3. Fidelity

    Document unsupported operations, semantic differences, timing, quotas, consistency, security, scaling, and failure behavior.12

  4. Lifecycle

    Own images, versions, ports, resources, persistence, seed data, cleanup, parallelism, logs, and real-service test stages.12

Local emulation routes

Select by provider architecture; Docker or Tilt may support the workflow but are not peer cloud emulators.

An AWS application needs broader local service emulation

Evaluate LocalStack.

LocalStack is the broad AWS route when local or CI workflows need several emulated AWS service APIs under one product.

Verify: Verify the exact services, features, parity, plan, image, persistence, networking, and real-AWS verification required by the application.1

An AWS SAM application needs a focused local serverless loop

Use AWS SAM CLI local commands.

AWS SAM CLI is the AWS serverless route when Lambda and API behavior around a SAM template is the specific local development job.

Verify: Containerized local invocation cannot prove every managed-service, IAM, network, scaling, event, quota, or deployment behavior.2

A Firebase application needs integrated local service testing

Use Firebase Local Emulator Suite.

Firebase Local Emulator Suite is the Firebase-native route for supported local products, rules, data, and application integration.

Verify: It is a development tool rather than self-hosted production; verify unsupported services and differences in performance, security, quotas, and production behavior.3

A Supabase application needs a local service stack

Use the Supabase CLI local stack.

Supabase CLI is the Supabase-native route when database, authentication, storage, and related local services should run together for development.

Verify: The local stack is development-only; the team owns Docker resources, migrations, seed data, version alignment, secrets, cleanup, and hosted-environment verification.4

Boundary: Development Environments owns the surrounding contributor workspace; Preview Environments owns remote deployed review instances using real or isolated services.

Differences that change the choice

Compare only the boundaries that materially alter adoption and ongoing ownership.

Provider scope
The candidates emulate different provider APIs and cannot be substituted by a generic local-cloud label.12
Fidelity
Supported surface and semantic parity vary by service, feature, version, and plan.12
Lifecycle
Images, containers, data, ports, parallel runs, cleanup, and state reset remain team responsibilities.12
Proof boundary
An emulator accelerates feedback but does not eliminate staged verification against real managed services.34

Official resources

Verify current product boundaries, control-plane behavior, execution limits, pricing, licensing, and operating requirements in first-party material before adoption.

Sources

Official product material supports the bounded routes and verification points; route selection remains an editorial judgment.

  1. 1
    LocalStack documentation

    LocalStack · Accessed Official

  2. 2
    AWS SAM local testing

    Amazon Web Services · Accessed Official

  3. 3
    Firebase Local Emulator Suite introduction

    Google · Accessed Official

  4. 4
    Supabase local development with CLI

    Supabase · Accessed Official

  5. 5
    LocalStack plans and licensing

    LocalStack · Accessed Official

  6. 6
    AWS SAM FAQ

    Amazon Web Services · Accessed Official

  7. 7
    Firebase pricing

    Google · Accessed Official

  8. 8
    Supabase pricing

    Supabase · Accessed Official