Expand description
§continuo
Agnostic service composition primitives for multi-service Rust applications.
No application state, no configuration, no HTTP, no TLS, no DB dependency.
Pull this crate into any Rust project with multiple services; bring your
own state type, implement state::SharedState and optionally
registry::ReloadState on it, then use registry::Registry with the
registry::Provider / registry::Reloadable /
registry::Runnable / registry::Finalizable traits.
The error model (registry::Error, registry::BoxError, registry::Result)
lives inside the registry module because it is a registry concern —
helper primitives such as [gate] have their own semantics and do not
share this error type.
Re-exports§
pub use registry::BoxError;pub use registry::Error;pub use registry::Finalizable;pub use registry::FinalizeFailure;pub use registry::FinalizeOutcome;pub use registry::Provider;pub use registry::ProviderOrder;pub use registry::Registry;pub use registry::ReloadFailure;pub use registry::ReloadOutcome;pub use registry::ReloadState;pub use registry::Reloadable;pub use registry::Result;pub use registry::Runnable;pub use registry::ValidationFailure;pub use registry::ValidationOutcome;
Modules§
Structs§
- RunContext
- Cancellation scope for one live generation of a
crate::Runnable. - Runtime
- Owns the live generations of every registered runnable service.
- Service
Manager - Cloneable control handle for runnable services owned by
crate::Runtime. - Service
Snapshot - Point-in-time view of a runnable service owned by the runtime.
Enums§
- Service
Manager Error - Service
Start Policy - Initial activation policy for one registered runnable service.
- Service
Status - Observable state of one registered runnable service.