WikiWIKI Graph
Wiki
Reference handbooks — evergreen content updated continuously
Browse Documents
61 documentsPatterns50 documentsOOP3 documentsidiom2 documentsC1 documentsDOP1 documentsFP1 documentsPolymorph1 documentsState1 documentsUML1 documents
All Documents
- IdempotencyTrace idempotence from algebra and fixed points to HTTP retries, request keys, and replicated state, with original sources.Patternspath:Patterns/Resilience & Flow Control
- InheritanceInheritanceOOPInheritance
- Interpreter PatternRepresent a small language as expression objects that evaluate their own meaning.Patternspath:Patterns/GoF/Behavioral
- Iterator PatternTraverse a collection without exposing its representation, using a separate object for traversal state.Patternspath:Patterns/GoF/Behavioral
- Mediator PatternCollect interaction rules in a mediator so collaborating objects do not depend directly on each other.Patternspath:Patterns/GoF/Behavioral
- Memento PatternKeep an opaque state snapshot so the original object can restore itself without exposing its internals to history management.Patternspath:Patterns/GoF/Behavioral
- MonadUse bind to connect computations that carry a context, such as absence, failure, multiple results, or asynchronous completion.Patternspath:Patterns/Functional
- MonoidCombine partial results with an associative operation and an identity, obtaining the same total regardless of grouping.Patternspath:Patterns/Functional
- MVC PatternAn architecture pattern that separates data and rules, presentation, and input interpretation into a model, views and controllers, assigning each a different reason to change.Patternspath:Patterns/Architecture
- MVP PatternA UI architecture pattern in which a presenter controls a screen through a view interface, so presentation rules can be tested without a UI.Patternspath:Patterns/Architecture
- MVU PatternAn architecture pattern that represents screen state as one value, updates it with a pure function that receives messages, and renders it with a view function.Patternspath:Patterns/Architecture
- MVVM PatternAn architecture pattern that connects a View and ViewModel through data binding, so screen state and actions can be handled apart from UI controls.Patternspath:Patterns/Architecture
- Object-Oriented ProgrammingObject-Oriented ProgrammingOOP
- Observer PatternNotify registered receivers of a change without making the source depend on every receiver.Patternspath:Patterns/GoF/Behavioral
- Option TypeRepresent possible absence in the return type instead of a null convention, requiring callers to handle both cases.Patternspath:Patterns/Functional
- Partial Application and CurryingFix some arguments to produce a function for the rest, and distinguish that operation from converting a function into a chain of single-argument functions.Patternspath:Patterns/Functional
- PolymorphismPolymorphPolymorph
- Programming IdiomsIdiomidiom
- Programming PatternsProgramming PatternsPatterns
- Prototype PatternCreate objects from configured prototypes with an explicit policy for copied and shared state.Patternspath:Patterns/GoF/Creational
- Proxy PatternControl creation or access through a substitute that exposes the same interface as the real object.Patternspath:Patterns/GoF/Structural
- Query FacadeQuery FacadePatternspath:Patterns/Data Access & Caching
- Rate Limiter PatternLimit requests per key over time and reject excess work before processing, using 429 and Retry-After.Patternspath:Patterns/Resilience & Flow Control
- Repository PatternPut aggregate storage behind a collection-like interface so business code remains independent of persistence technology.Patternspath:Patterns/Data Access & Caching
- Result TypeReturn either a success value or a failure reason, making failure explicit data rather than relying on exceptions.Patternspath:Patterns/Functional
Recently Updated
- C++ IdiomsC++ Idioms
- Mediator PatternCollect interaction rules in a mediator so collaborating objects do not depend directly on each other.
- Memento PatternKeep an opaque state snapshot so the original object can restore itself without exposing its internals to history management.
- Flyweight PatternShare repeated immutable state while keeping per-use data such as position separate.
- Composite PatternTreat an individual item and a group of items through the same component contract.
- Interpreter PatternRepresent a small language as expression objects that evaluate their own meaning.
- Visitor PatternAdd operations as visitor objects when the kinds of elements in a structure are relatively stable.
- Chain of Responsibility PatternPass a request along handlers until one accepts it, with an explicit unhandled result.