C++ Boost lifecycle

Boost.Asio coroutine makers, generated HTTP activation, graph drain, and runtime release.

When to use

Use this page when implementing maker hooks, owning resources, or diagnosing startup and shutdown.

Generated makers return boost::asio::awaitable results before graph activation.
initRuntime constructs router, server, clients, functions, streams, and endpoint bindings.
ServiceApp::start activates resources; generated HTTP admission opens afterward.
Stop drains graph work while callers and streams live, then stops Sinks and execution runtime.

ConfigurationLoad graph configResolve typed service, stream, connector, and endpoint settings.

FactoriesinitMakersInstall defaults, then run customMakersInit and serviceStarted.

ConstructionInvoke makers onceCreate infrastructure and long-lived functions in parallel.

GraphBuild and bindConstruct streams, callers, endpoint consumers, and transports.

StartOpen admission lastStart dependencies and Sinks before Sources and servers.

SignalStop requestedCreate one deadline from shutdownTimeout.

AdmissionListeners and SourcesReject new root work and drain accepted calls.

GraphNested workKeep pools, storage, Sinks, and clients alive.

ResourcesPools, storage, SinksRelease graph dependencies in safe order.

TelemetryFlush and releaseMetrics, traces, and logs stop last.

The generated HTTP server uses the service shutdown timeout.
Graph callbacks may emit results while draining, so Sinks stay alive.
stopRuntime and releaseRuntime cover normal stop, rollback, and destruction.

Generated extension points and runtime-owned lifecycle boundaries.

PropertyTypeDescription

initMakersgenerated

Assigns coroutine factories.

customMakersInitvirtual hook

Replaces factories before invocation.

initRuntimegenerated

Awaitably creates objects and binds graph.

http_server_->Startadmission

Opens HTTP after ServiceApp is ready.

stopRuntimegenerated

Coordinates server stop, drain, and release.

configure -> make once -> bind -> start -> admit -> drain -> stop