CERK lets you route your CloudEvents between different different ports. Ports are transport layer bindings over which CloudEvents can be exchanged. It is built with modularity and portability in mind.
CERK comes with a couple of prefabricated components, but implementing custom components is easy.
A good overview is provided on GitHub.
The MicroKernel is responsible for starting the other components with the help of the Scheduler and brokering messages between them.
The MicroKernel is implemented in this crate.
Implementation of the core components of CERK
Runtime definitions for CERK. The implementations for the declarations could be platform-specific.