Data-Oriented programming
summary
Argues that refactoring a Java library-management design into split data and code (plain data classes + separate functions) removes tangled methods, eliminates many locks and race conditions, and reduces object graph complexity from dozens of interlinked classes to simple value records. Shows using immutable collections and auto-generated constructors, and using immutable data values plus map/filter/reduce for polymorphism to replace inheritance. Claims measurable wins: fewer state bugs, easier concurrency, and simpler maintenance in production systems.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:01Complex system OOP example
- 5:54Traditional data-class problems
- 8:46Static method complexity
- 12:00Locking mechanisms drawbacks
- 13:47Simplifying code solutions
- 16:39Benefits of simple immutable systems
- 19:09Conclusion
related talks
49mData-oriented Programming in Java
47mData-oriented programming in Java
40mReduce System Complexity with Data-Oriented Programming
58m#OOP vs Data Oriented Programming Which One to Choose
25mOOPs!... I Did it Again: When Good Objects Go Toxic
51mFunctional Principles for Object Oriented Development
01h 00mOOP vs Data Oriented Programming: Which One to Choose?
01h 05mFrom object oriented to functional domain modeling
