Overview

Corvis has no microservices layer: there are no transports, no ClientProxy, no message patterns (@MessagePattern/@EventPattern) and no hybrid applications that listen on HTTP and a broker at the same time.

Alternative

You can consume or publish messages with your broker's Rust client inside a regular provider:

• Create the client with an async factory (Provider::use_factory), reading the connection from ConfigService.
• Start consuming in OnApplicationBootstrap (spawning a task with corvis::tokio::spawn) and stop consuming in BeforeApplicationShutdown or OnApplicationShutdown; call app.enable_shutdown_hooks() so they run on SIGINT/SIGTERM.
• For a process that only consumes, without listening on a port, see Standalone applications: today create_application_context does not register the #[on_event], #[cron], #[interval] or #[timeout] handlers, so consumption must start from a lifecycle hook.
• Within the same process, EventEmitter and #[on_event] decouple producers and consumers (see Events).

See Lifecycle events and Async providers.