Patterns

Recurring solution structures for problems that appear in software design.

Entries (6)

Adapter patternTranslate one interface into another when useful behavior exists behind an incompatible boundary.

Design provider-neutral integration boundariesExpose external capabilities through application-owned contracts when provider details should not define the domain.

Observer patternNotify dependent consumers when a subject changes without hard-coding each consumer into the subject.

Separate canonical domain entities from provider representationsModel stable domain identity separately from records owned by external providers.

Separate current state from observation historyServe current reads from compact state while preserving append-only observations for history and provenance.

Strategy patternEncapsulate interchangeable algorithms behind one contract so a context can vary behavior without owning each implementation.