continuo 0.10.0

Runtime service composition for multi-service Rust applications: typed component resolution, dependency-ordered lifecycle, reload, runnable tasks, graceful drain, and finalization.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

use async_trait::async_trait;

use super::Result;

/// Ordered, finite preparation before runtime work is admitted.
///
/// `D` is the component's `Deps`, resolved by the registry and passed in; the
/// hook does not look its dependencies up. It consumes validated
/// configuration, constructs complete objects and publishes their handles. A
/// preparation component may prepare several related objects; those objects
/// need no boot hook of their own.
///
/// No listener, detached task or operational loop starts here; that work
/// belongs to a runtime-owned `Runnable`. Expose this capability through
/// `Component::as_bootable`; implementing the trait alone neither inserts an
/// object into DI nor registers it for execution.
#[async_trait]
pub trait Bootable<S, D = ()>: Send + Sync {
    async fn boot(
        &self,
        deps: D,
        state: &S,
    ) -> Result<()>;
}