Putting off Persistence
summary
Claim: postpone choosing a database until the domain is understood. Implements simple in-memory repository and an event list backed by arrays and small classes, drives behavior with Cucumber features, then swaps in an ActiveRecord adapter for production. Shows how this cuts migrations and DB hacks, forces collection APIs and composition (date-range object), and lets different models use different datastores while keeping tests fast and the domain code insulated.
AI-written summary · about
chapters (13)
- 0:00Start
- 5:07Event Scenarios
- 5:24Event Step Definitions
- 5:46Events Controller
- 6:37Event View
- 9:18Scoping Event Code
- 9:42Event Controller
- 13:21Cucumber Features
- 13:47More Cucumber Steps
- 17:21Event Model
- 17:41EventList!
- 33:52Event Class
- 35:47Active RecordEventList
related talks
35mPersisting Relations Across Time and Space
30mWould you like to forget about the database?
36m"Persistence pays off: a new look at rom-rb"
32mRuby Preserves
28mPersistence Has Its Limits
35mPersistence pays off: a new look at rom-rb
50mCreate Your Perfect Persistence Stack
46mThe State of Java Relational Persistence