add-eventbridge

Publishing tenant-aware domain events to EventBridge involves using a publisher that propagates a tenantId and enforces typed schemas for multi-tenant microservices. This pattern enables decoupled services to communicate asynchronously across bounded contexts with per-tenant routing.

Handling asynchronous domain events across bounded contexts requires a shared bus with typed schemas and tenant context propagation. Using a publisher and optional consumer via SQS provides a consistent pattern for scalable intra-organization event-driven communication.

Configuring an EventBridge publisher and consumer requires wiring them in your service using environment-based configuration templates. You then emit an event after a write operation, allowing the optional SQS consumer to process the tenant-aware domain event downstream.

Yes, you can use SQS to consume EventBridge domain events for decoupled microservices. The skill implements an optional consumer via SQS, enabling scalable intra-organization event-driven communication with tenant-aware context and typed schemas.

Yes, the EventBridge publisher supports batch publishing and enforces error handling for domain events. It uses environment-based configuration to ensure type-safe domain events are reliably emitted to a shared bus with tenantId propagation.

You need tenant-aware domain events in an event-driven architecture when a domain entity changes, such as domain.created, and you must emit an event to trigger downstream processes like indexing, notifications, or analytics across tenants.