26 major breaking releases
| 28.0.0 | Dec 19, 2025 |
|---|---|
| 27.0.0 | Dec 8, 2025 |
| 26.0.0 | Oct 3, 2025 |
| 25.0.0 | Aug 2, 2025 |
| 0.0.0 |
|
#1 in #overseer
12,444 downloads per month
Used in 76 crates
(18 directly)
1MB
20K
SLoC
Overseer
overseer implements the Overseer architecture described in the
implementers' guide.
For the motivations behind implementing the overseer itself you should
check out that guide, documentation in this crate will be mostly discussing
technical stuff.
An Overseer is something that allows spawning/stopping and overseeing
asynchronous tasks as well as establishing a well-defined and easy to use
protocol that the tasks can use to communicate with each other. It is desired
that this protocol is the only way tasks communicate with each other, however
at this moment there are no foolproof guards against other ways of communication.
The Overseer is instantiated with a pre-defined set of Subsystems that
share the same behavior from Overseer's point of view.
+-----------------------------+
| Overseer |
+-----------------------------+
................| Overseer "holds" these and uses |..............
. them to (re)start things .
. .
. +-------------------+ +---------------------+ .
. | Subsystem1 | | Subsystem2 | .
. +-------------------+ +---------------------+ .
. | | .
..................................................................
| |
start() start()
V V
..................| Overseer "runs" these |.......................
. +--------------------+ +---------------------+ .
. | SubsystemInstance1 | | SubsystemInstance2 | .
. +--------------------+ +---------------------+ .
..................................................................
Dependencies
~110–155MB
~2.5M SLoC