Skip to content

stevenacoffman/software-design

v0.1.0MIT

Software design and refactoring: deep modules, information hiding, and incremental change.

strong-consistency-across-bounded-contexts

Apply when designing inter-service communication or choosing sync vs async coordination, especially when reaching for a distributed transaction or synchronous RPC to update another bounded context atomically. Prefer eventual consistency across contexts.

Read SKILL.md at the source

Pinned to revision e4081cbb4d29, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.