Implements a .NET outbox for reliable event publishing with inbuilt error handling and logging.
npx skills add https://github.com/yeeehaooo/WorkSpace --skill outbox
Please help me install this Agent Skill. Skill: outbox Source: https://github.com/yeeehaooo/WorkSpace/tree/main/skills/dotnet/patterns/outbox Command: npx skills add https://github.com/yeeehaooo/WorkSpace --skill outbox
Ensure reliable event publishing and message delivery by storing events in the same transaction as domain changes, solving the dual-write problem.
Use Case: Imagine an e-commerce workflow where orders and related events must be published reliably even if the application crashes.
Start by wiring your domain events into the outbox within your unit of work, then run the OutboxPublisher in the background to deliver events reliably.
High-intent search queries and answers about installing and using this skill.
It solves the dual-write problem by persisting domain events in the same transaction as state changes. This guarantees reliable event publishing and eventual consistency across distributed services even if the application crashes.
Wire domain events into the outbox within your unit of work, then run a background publisher. The publisher reads unpublished messages and publishes them to the message broker or event bus with retry logic and idempotent handling.
It achieves eventual consistency through idempotent handling and retry with backoff. This ensures that duplicate message deliveries to the event bus do not create duplicate side effects across distributed services.
You need an outbox for distributed systems requiring guaranteed delivery and eventual consistency across services. It is essential whenever dual-write concerns threaten atomic state changes and event publishing in event-driven workflows.
Yes, it implements the outbox inside the Application and Infrastructure layers. This maintains clear separation of concerns across Domain, Application, and Infrastructure layers while isolating domain logic from messaging infrastructure.
The main limitation is delivery latency, as a background publisher reads and publishes messages asynchronously. While retry with backoff handles transient broker failures, the system achieves eventual consistency rather than immediate real-time delivery.
FaysilAlshareefPersist domain events and outbox messages atomically in .NET microservices.
lcmassenaPublish JSON-serialized domain events to Azure Service Bus topics with sessions and scheduled delivery.
hung-phanImplement a transactional outbox pattern for atomic event publishing.
cornmanwtfImplement change data capture and event-driven synchronization patterns for data integration.
