WikiWIKI Graph
Wiki
Reference handbooks — evergreen content updated continuously
Browse Documents
6 documentsPatterns
Documents
- Architecture PatternsA guide to UI architecture patterns (MVC, MVP, MVVM and MVU), with a short introduction to layered, hexagonal, onion and clean architecture.Patternspath:Patterns/Architecture
- Backend for Frontend (BFF) patternTrace BFF adoption and naming, then follow this website's architecture and UML through its web proxy, BFF cache, and content service.Patternspath:Patterns/Architecture
- 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
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.