Architectural depth
Ergo: a composable model for event processing.
An architectural approach developed through years of building event-driven systems—not a product clients must adopt.
Central premise
Useful work should not understand the machinery around it.
Delivery, execution, routing, retry, storage, and deployment surround business behavior rather than contaminating it.
Ordinary behavior
Functions remain functions.
A worker can receive ordinary arguments, return domain values, and raise exceptions. It need not know RabbitMQ delivered the input, NATS will carry the output, or infrastructure resolved credentials and storage.
Composable processing
Small stages, narrow responsibility.
Ingress can receive and durably own work; execution can materialize data and invoke behavior; egress can publish through a different system. Explicit contracts let individual links be replaced without redesigning the whole.
Transport independence
Messaging technology is infrastructure, not business semantics.
RabbitMQ, NATS JetStream, durable database queues, cloud buses, or future transports can satisfy different deployment needs without rewriting domain functions.
Architectural evidence