Analysis
Compare patterns
Evaluate design patterns side by side across intent, tradeoffs, languages, and integration fit.
Choose patterns
Select up to 3 patterns
Current selection
3 of 3 selected
You can now review the differences across the comparison table below.
Analysis
Pattern comparison
Reviewing 3 patterns.
| Criteria | |||
|---|---|---|---|
| Basics | |||
| Category | behavioral | behavioral | behavioral |
| Summary | — | — | — |
| Intent | Capture and externalize an object's state so it can be restored to a previous point in time. | Define a subscription mechanism so multiple observers can react to subject events without the subject knowing concrete subscriber details. | Encapsulate a family of algorithms or behaviors behind a common contract so they can be selected and swapped cleanly. |
| Decision factors | |||
| Problem | An object's internal state must be saved and restored later without exposing its implementation details. | A system needs to notify multiple dependent objects when state changes occur, but hardcoding those dependencies makes the design rigid and tightly coupled. | A system needs to switch between interchangeable behaviors without hardcoding branching logic everywhere. |
| Tradeoffs |
|
|
|
| Practical fit | |||
| Languages |
|
|
|
| Platforms |
|
|
|
| Integration notes | Memento is useful for undo/redo, checkpoints, draft recovery, and any workflow where state history matters. | Observers work well inside a single application boundary for UI events, domain events, and in-process notifications where subscribers change dynamically. | Strategies can cross codebases through shared contracts, API selection rules, or runtime configuration. |