docs(service-communication): reference — choosing a communication mechanism#51
Merged
Merged
Conversation
…n mechanism Add a capstone reference page that puts Connectum's three orthogonal cross-service mechanisms side by side and helps pick the right one per interaction: - ctx.call / ctx.stream — synchronous, when you need the answer to proceed - EventBus — asynchronous fire-and-forget, when you announce a fact - durable saga (Temporal) — a multi-step transaction with LIFO compensation The page frames the decision around coupling-in-time and failure semantics (not performance), gives a decision table + a per-mechanism trade-off, shows the three composed in one flow (a Mermaid diagram), and points at the car-sharing and hris reference examples. It reinforces the "framework stays thin" stance: ctx.call and EventBus ship in the framework; durable orchestration is delegated to a best-of-breed engine rather than reinvented. Registered first in the Service Communication sidebar group. Builds clean (vitepress build, no dead links). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MdeH7fExPmiRHRirGuvGk3
intech
force-pushed
the
docs/communication-mechanisms-reference
branch
from
27f438f to
06105f7
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
A new capstone reference page — Choosing a Communication Mechanism — that puts Connectum's three orthogonal cross-service mechanisms side by side and helps a reader pick the right one for each interaction (no existing page covers this decision):
ctx.call/ctx.stream(synchronous)The page frames the decision around coupling-in-time and failure semantics (not performance), gives a decision table and a per-mechanism trade-off, shows the three composed in one flow (a Mermaid diagram), and points at the
car-sharingandhrisreference examples. It reinforces the framework-stays-thin stance:ctx.calland EventBus ship in the framework; durable orchestration is delegated to a best-of-breed engine (Temporal) rather than reinvented.Registered first in the Service Communication sidebar group.
Verification
vitepress buildis clean — all internal links resolve (VitePress fails the build on dead links), Mermaid diagrams render, the page is emitted todist/.ctx.call, the EventBus, and the saga pattern, all demonstrable on the published packages (no unpublished-1.1.0 API).Cross-repo note
The page's three-mechanism reference to hris assumes examples #31 (the hris onboarding saga, Phase 5a) is merged; the car-sharing trip-saga reference is already on examples
main. Both example links point to themainbranch of the examples repo.🤖 Generated with Claude Code
https://claude.ai/code/session_01MdeH7fExPmiRHRirGuvGk3