High Optionality Programming: software architectures that reduce technical debt

on YouTube ↗01h 06m

" summary

Argues that architectures preserving choices cut technical debt, showing concrete moves: moving from RavenDB-tied code (10k → 5–8M events/day caused map-reduce indices to go stale for 2–3 days) to an event-driven pipeline that emits analytic deltas, separates read/write via CQRS, and abstracts persistence so databases can be swapped. Describes using Akka.NET actors for per-entity, thread-safe event processing, event sourcing to replay history, and extend-only schemas to avoid breaking migrations and enable zero-downtime upgrades.

AI-written summary · about

" chapters (11)

1. 0:00Introduction
2. 2:58What is technical debt
3. 8:56Optionality in software
4. 13:11High optionality programming
5. 19:31Event-driven programming benefits
6. 27:52Event sourcing advantages
7. 35:31CQRS and decoupling
8. 43:18Actors for scalability
9. 52:25Extend-only design
10. 58:18Common high optionality traits
11. 1:00:03Conclusion and Q&A

" related talks

• 49mGetting a handle on software architectureTomer Gabel · Build Stuff 2021
• 49mRethinking Reactive ArchitecturesDavid Leitner · Devoxx Ukraine 2021
• 38mAgile ArchitectureMartin Fowler, Molly Dishman · O'Reilly Software Architecture Conference 2015
• 18mPlatform-Oriented Legacy ModernizationAnanth Subramanya · Aerospike User Summit 2018
• 55mUnderstanding Modern Trade-off Analysis in Software ArchitectureNeal Ford · Software Architecture Gathering – Digital 2023
• 36mApplication Architecture PatternsJoe Guadagno · Code Quality Conference 2022
• 58mEffective Architecture Practices DebateÁlvaro García · Global Software Architecture Summit 2019
• 54mSoftware architecture evolution, what to expect? Panel DiscussionGlobal Software Architecture Summit 2019