Story: Complete the pattern language
Table of Contents
This page documents a story in Sprint 27. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
The pattern language is complete: the communication, coordination, resilience, load and data pattern groups are written, each pattern naming its established name and its sources, and a design names its patterns as a rule rather than by memory. The type, the hub, the identity patterns and the reporting design shipped with the source story.
This story was split from A pattern language for service interaction when that story was reworded to the language it delivered and closed DONE at the sprint 26 close on 2026-10-05; its two remaining tasks moved here.
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 27 |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-10-05 |
3. Acceptance
- The communication, coordination, resilience, load and data groups exist, each pattern naming its established name and its sources.
- A design names its patterns, and the knowledge index links every group.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Make a design name its patterns | DONE | 2026-10-05 | 2026-10-05 | A memory that a design names its patterns from the hub, and a patterns-used section in the knowledge and workflow types. |
| Write the communication, coordination, resilience, load and data patterns | DONE | 2026-10-05 | 2026-10-05 | Request-reply, correlation identifier, claim check, competing consumers, saga, process manager, idempotent receiver, timeout, retry, bulkhead, circuit breaker, load levelling, throttling, fair share, database per service and cache-aside. |
5. Decisions
- Circuit Breaker is not in the language. The hub lists a pattern only when ORE Studio uses it or a design has chosen it, and no service or design uses a circuit breaker. A design that chooses one adds its page first, as the memory on naming patterns requires.
- Uses and patterns come from one table. The pages and the back-links on their
use pages were generated together, so the two directions start in agreement,
and
build/scripts/check_pattern_uses.pykeeps them so.
6. Out of scope
7. Result
Done: every group of the pattern language is written, and a design names its patterns by rule.