Local cloud emulation
Replicating cloud service APIs and behaviors on local infrastructure so applications and tests run without connecting to remote cloud services.
Glossary
The vocabulary of local cloud development — defined once, used consistently across the registry and architectures.
Core Concepts
Emulator
Software that implements a cloud service's actual behavior — state, error semantics, API contracts — rather than returning canned responses.
Local cloud development
The workflow built on top of emulation: running services in CI, testing infrastructure-as-code, persisting and seeding state, and validating permissions — all before anything reaches a real cloud account.
Mock
A stand-in that returns predefined responses for specific requests. Useful for unit tests; unlike an emulator, it verifies that code calls an API, not that code works against the service's behavior.
Local cloud sandbox
An isolated, on-demand environment running on local infrastructure that replicates cloud service behavior, letting developers test cloud applications without deploying to remote infrastructure.
Quality & coverage
Service coverage
The degree to which a cloud service's APIs and behaviors are implemented by an emulator. Coverage describes what is implemented.
Benchmark Criterion
Parity
The degree to which an emulator's behavior matches the real cloud service for a specific service, API, or scenario. Parity describes how faithfully — and is meaningless without scope: "full parity" claims should always name the service and scenario.
Parity testing
Continuously testing an emulator against the real cloud API to catch drift, so the emulator keeps behaving like the service it stands in for.
Benchmark Criterion
Snapshot testing
Locking recorded API responses so an upstream change can't silently break a test suite.
Benchmark Criterion
Fault injection
Deliberately simulating service disruptions, degraded conditions, and outages in a local environment to validate resiliency before production.
Benchmark Criterion
Environments
Local environment
A developer's own machine, used for development and testing. Not the same as on-premises infrastructure.
CI environment
The runner within a continuous integration pipeline where automated builds and tests execute. A component of the pipeline, not a synonym for it.
Staging environment
A persistent pre-production environment used for integration validation before promotion.
Preview environment
A temporary environment created to validate a specific change or pull request, torn down after validation. Not staging.
Ephemeral environment
Any short-lived, disposable environment created on demand for a validation or testing workflow.
Air-gapped
Operating in complete network isolation, with no outbound connectivity. Stricter than "offline," which usually still permits periodic checks.
Workflows
Inner loop
The rapid code → run → test cycle a developer executes locally before pushing changes. Faster inner loops mean more iterations per hour.
Feedback loop
The time between making a change and seeing its result. The core metric local emulation improves.
IaC parity
Infrastructure-as-code (Terraform, Pulumi, CDK) applying locally the same way it would against a real cloud account.
Benchmark Criterion
Integration tests
Tests verifying that multiple services work together correctly, typically against a realistic environment. Distinct from end-to-end tests, which verify complete user-facing workflows.
Misconfiguration
An incorrect cloud configuration causing failures, outages, or vulnerabilities. A configuration error, not an application bug — and a leading cause of production incidents.
No terms match your search.