Life After Business Objects - Confessions of an OOP Veteran

on YouTube ↗35m

" summary

Team replaces mutable Business Objects with F# and immutable records to process gigabytes of live TV radio and podcast data per hour, moving logic into small modules and functions instead of methods on big classes. Domain modeling uses algebraic data types and phase-specific record types to remove options and avoid nulls. Resulting service shortens spec-to-production, yields about 50% less code and fewer bugs, and gives safer concurrency and easier testing without external DBs for core logic.

AI-written summary · about

" chapters (13)

1. 0:00Introduction
2. 1:15Being Pragmatic
3. 2:05Reference
4. 2:24Point
5. 6:10Posture concurrency
6. 7:18Visibility qualifier
7. 8:27Point manager
8. 10:03Business objects
9. 12:38Implementation
10. 14:41ObjectOriented Paradigm
11. 16:10Domain Modeling
12. 23:07Options
13. 25:44Data Structure

" related talks

• 34mLife After Business Objects - Confessions of an OOP VeteranVagif Abilov · GOTOpia November 2020
• 37mLife After Business Objects: Confessions of an OOP VeteranVagif Abilov · GOTO Copenhagen 2021
• 44mLife after business objects. Confessions of an OOP veteranVagif Abilov · Build Stuff 2020
• 59mLife After Business ObjectsVagif Abilov, Maksim Arshinov · DotNext 2019 Piter
• 37mDomain modelling in object-oriented and functional programming, based on C# and F#Marcin Kern · NDC Oslo 2022
• 29mSingle Value Objects: where DDD and Functional Programming Share ForcesCorniel Nobel · Build Stuff 2020
• 52mBreaking Bad Code: From simple problems to complicated solutions and backWojtek Ptak · JDD 2023
• 52mF# in the real worldYan Cui · Lambda World 2015