Convenience vs Simplicity
summary
Argues for separating concerns: treat data as relations first, use relational algebra for composition, and keep persistence mapping separate rather than stuffing behavior into models. Demonstrates Ruby Object Mapper (ROM) built on axiom, offers optional mapping to objects, and distributes inserts across tables. Advocates immutable data with ice_nine and object freezing via adamantium, notes both reduce bugs but cost performance. Labels the approach experimental yet useful on growing apps and warns optimizer work remains to make queries fast.
AI-written summary · about
chapters (34)
- 0:00Introduction
- 3:28Convenience vs Simplicity
- 7:28Internal complexity
- 15:40Minimalism
- 16:08Mutability
- 17:16Dupris
- 18:09Atomium
- 22:23Relational Model
- 23:47Relational Model Libraries
- 23:57Axiom
- 25:01Relational Operations
- 25:27Join Two Relations
- 25:53Data Independence
- 26:33First Class Citizens
- 26:46ActiveRecord
- 27:40Relations
- 27:52Relation Registry
- 28:36Better composability
- 29:20Find all users
- 30:13Scopes
- 31:01First Class Citizen
- 31:22Relational Operators
- 32:31Ruby ObjectMapper
- 33:10Data Relations
- 33:44Mapping to Objects
- 35:15Logical Schema
- 36:29External External Relations
- 38:04Mapping
- 39:06Embedded Values
- 40:03Simplicity
- 40:46Summary
- 41:17Simple interface
- 41:59Embrace simplicity
- 42:21Questions
