Expand description
Lambda execution runtime — pluggable backend behind a shared facade.
LambdaRuntime owns the warm-pool bookkeeping and the HTTP
invocation path. The actual lifecycle (container/pod create, port
discovery, teardown) is delegated to whatever LambdaBackend the
facade was constructed with — today that’s DockerBackend; a
Kubernetes backend ships in a follow-up.
Re-exports§
pub use k8s::K8sBackend;pub use k8s::K8sBackendError;
Modules§
- k8s
- Kubernetes
LambdaBackendimplementation.
Structs§
- Docker
Backend - Docker/Podman-based Lambda execution backend.
- Lambda
Runtime - Streaming
Invocation - Wrapper around an in-flight streaming invocation. Yields raw body
chunks via
Self::next_chunkuntil the RIE closes the response, at which point the finalOk(None)signals the caller to emit the terminalInvokeCompleteframe. - Warm
Instance - What
LambdaBackend::launchreturns.endpointis thehost:portthe facade POSTs invocation payloads to;handleis the backend-specific identifier handed back onterminate.
Enums§
- Backend
Handle - Opaque per-backend identifier for a launched runtime instance. The facade hands this back to the backend on teardown so the backend can find the right resource to delete.
- Runtime
Error
Traits§
Functions§
- extract_
zip - Extract a ZIP archive to a destination directory.
- runtime_
to_ image - Map AWS runtime identifier to a Docker image tag.
Type Aliases§
- Container
Runtime - Backwards-compatible alias used by callers across the workspace (eventbridge bridge, scheduler, lambda_delivery, reset state, server main). Keeping the old name lets the trait extraction land without churn in every consumer.