From Irrational Configuration System to Functional Data Store
summary
Begins with 42 Oracle tables, 5200+ configuration values, a 1.5 million–line Java legacy and onboarding that runs up to 10 months and claims anyone who touches config will be gone in six months. Replaces it with a custom immutable, time‑variant functional data store using event sourcing and CQRS, projecting views into Oracle and treating Oracle as an event source for backward compatibility. Production prototype is Java (one process per book), development moves to Elixir with one actor per key, RabbitMQ for messaging, Metalsmith for toolsite, and proven in limited rollout.
AI-written summary · about
chapters (7)
- 0:00Start
- 5:48Reducing Complexity
- 8:56Functional First Programming
- 24:30Configuration Management
- 24:40Configuration Management Tool
- 25:34Goals for Configuration Management
- 29:01The Tyranny of the Database
related talks
51mImmutable data stores and CORS for safety, flexibility and profit
16mSurviving without a database framework
12mTen Things I Hate About Microservices
22mSimplify data and event-driven microservices with Oracle Database
39mRethinking RDBMS Data Migration
24mRethinking Database Architecture to Embrace Modern App Dev
42mA Practical Functional Relational Architecture
37m11 insights after 11 years with the functional database Datomic
