Skip to content

CONCEPT Cited by 1 source

Local emulation

Definition

Local emulation = running a faithful-enough substitute for a cloud service on the developer's local machine so that application code targeting the real service's API can be validated without a cloud round-trip. Umbrella concept covering Lambda + API Gateway emulation via SAM (sam local start-api), same-image container runs replacing ECS/Fargate, DynamoDB Local for CRUD/query/stream tests, and AWS Glue ETL libraries shipped as Docker images for data-pipeline iteration.

Why it's load-bearing for agents

Named by the 2026-03-26 AWS Architecture Blog post as "the default feedback path" for AI-coding agents:

"Local emulation reduces iteration time, allowing AI-generated code to be validated in seconds and potentially reducing the cost and risk of experimentation."

The structural property is API-shape parity: the emulator speaks the same wire protocol as the production service, so the application SDK calls are unchanged across local and cloud. Changes propagate at subprocess latency (start container, run test) instead of deploy latency (minutes).

What local emulation does and doesn't give you

Gives you:

  • Same SDK, same API, same success / error shapes.
  • No network hop, no IAM, no billed capacity, no rate limits.
  • Deterministic teardown — each test run starts fresh.

Doesn't give you (canonical drift classes):

  • Cold-start / warm-start timing semantics — Lambda cold-start behavior, container pull-latency, regional failover.
  • IAM / resource-policy runtime errors — smoke tests in the real cloud exist precisely because these only surface there.
  • Scale behavior — local emulation is a correctness oracle, not a performance model.
  • Cross-service race conditions — only reproducible against real services with real clocks, real queues, real retries.

The 2026-03-26 AWS post acknowledges this boundary obliquely: "Some AWS services cannot be fully emulated locally. In these cases, the goal is not to avoid the cloud, but to keep cloud feedback lightweight" (patterns/hybrid-cloud-testing). A related articulation is Dropbox Nucleus's Rust-backend-mock suite, Heirloom, running at ~100× slowdown vs production — see systems/dropbox-nucleus.

Canonical local emulators named in the 2026-03-26 post

  • systems/aws-sam — Lambda + API Gateway via sam local start-api / sam local invoke.
  • Same-image container run — ECS / Fargate workloads via docker run with the same image.
  • systems/dynamodb-local — Java-based DynamoDB emulator persisting to SQLite.
  • systems/aws-glue Docker images — ETL libraries packaged so Glue jobs run locally against sample data.

Seen in

Last updated · 200 distilled / 1,178 read