feat: Add Event-Driven Architecture semantic anchor#143
Conversation
Adds EDA as a standalone semantic anchor covering async decoupling via events, publish-subscribe, and message queues. Based on Hohpe/ Woolf's Enterprise Integration Patterns. Distinct from CQRS (read/write separation), Observer (single-process, synchronous), and Event Sourcing (state storage, not communication).
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Review: ✅ Good anchor, merge-ready. Event-Driven Architecture is a well-defined architectural style with clear attribution (Hohpe/Woolf EIP, 2003). Strong content — the choreography vs. orchestration distinction is particularly valuable as a semantic anchor for LLM communication. Post-merge TODO:
Merging recommended, translation will follow in batch (see #149). |
LLM-Coding#138, LLM-Coding#139) Content from @Nantero1's original PRs LLM-Coding#138 and LLM-Coding#139, rebased on current main after merging LLM-Coding#137, LLM-Coding#140, LLM-Coding#142, LLM-Coding#143. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Summary
Why this anchor?
EDA is a foundational architectural style with zero coverage in the catalog. It activates: event producers/consumers, publish-subscribe, async decoupling, message queues, at-least-once delivery, idempotency, eventual consistency, choreography vs. orchestration.
The catalog already has architectural anchors (Hexagonal, Clean, DDD) but none covering event-based communication — a gap given how pervasive async messaging is in modern systems.
Key separations from existing anchors:
Files changed
docs/anchors/event-driven-architecture.adoc— new anchor filedocs/all-anchors.adoc— added include in Software Architecture sectionskill/semantic-anchor-translator/references/catalog.md— added catalog entry