Java Evolution Vector: DOP
summary
Shows an implemented composite hierarchical access checker that starts as a Java 11 registry+strategy mess with Jackson and Spring Data JDBC, then is refactored through sealed classes, records, and pattern-matching switch with inline deconstruction; Java 11 produces lots of boilerplate and brittle tests, Java 17 reduces some friction but has impedance with Hibernate, and Java 21+ removes instanceof noise and makes the dispatcher exhaustive and safer — the evolved system compiles cleaner and behaves correctly.
AI-written summary · about
chapters (19)
- 0:00Introduction and welcome
- 2:33What is data oriented programming
- 5:08Data oriented vs object oriented
- 8:19Data processing flow in apps
- 11:56Data oriented principles
- 16:18Access control system example
- 18:32Java 11 implementation
- 21:45Issues with Java 11 approach
- 26:45Java 17 features impact
- 29:16Pattern matching basics
- 31:08Algebraic data types
- 33:17Pattern matching in Java 11
- 34:20Pattern matching in Java 21
- 36:09Refactoring with Java 21
- 37:11Java 22 unnamed patterns
- 38:19Java 23 features preview
- 40:26When to use data oriented programming
- 42:11Java version recommendations
- 42:32Summary and conclusion
