Software Architecture
When Undo/Redo Stops Scaling: Transactional History for Object Graphs
Full-document snapshots are a valid undo/redo boundary—until a large, shared object graph makes every small edit pay for the whole document. Transactional copy-on-write history narrows that work, but introduces a real management cost.
- .NET
- Undo/Redo
- Object Graphs
- Copy-on-Write
- Transactions
- Performance
Sep 14, 2026
Read article