ores::eventing Namespace Reference

In-process event bus — decoupled communication within a single process. More...

Namespaces
namespace	domain
	Domain types for the eventing infrastructure.
namespace	generators
	Test data generators for eventing types.
namespace	service
	Event bus and related services.

Detailed Description

In-process event bus — decoupled communication within a single process.

Provides type-safe publish/subscribe between components running in the same process (e.g. handlers inside ores.comms.service, or between service layers). Does not cross process boundaries and has no network dependency.

• domain sub-namespace: event_traits<T> — compile-time mapping from a C++ event type to its string name (e.g. "ores.refdata.currency_changed"). Also defines entity_change_event, the common payload for all domain change notifications.
• service sub-namespace: event_bus — thread-safe in-process pub/sub. postgres_event_source bridges PostgreSQL LISTEN/NOTIFY into the event bus so that database-side changes (triggers, pg_notify) raise in-process events without polling.

The event_traits string names defined here are reused as NATS subject suffixes by ores.nats when publishing events to external subscribers.

Contrast with ores.nats (external NATS bus, cross-process) and ores.mq (durable PostgreSQL-backed queues, persistent across restarts).