SOLID Golden Hammer
summary
Argues for a concrete Rails architecture that splits data and logic into two kinds of objects: typed structures (uses dry-struct, Money gem types) and small stateless behaviors with a single call method (built with dry-initializer), passing DTOs and a uniform params+context interface. Shows a gateway layer (Faraday-based requests and typed responses), a composable sequence pipeline and transaction component, extraction of persistence, and an example e‑commerce order flow where each step is replaceable and testable.
AI-written summary · about
chapters (14)
- 0:00SOLID Golden Hammer intro
- 1:09Rails app growth problems
- 2:36Services don't solve architecture
- 4:02SOLID and OO patterns
- 6:11Golden hammer explained
- 9:00Live e-commerce demo
- 12:09Gateway boundary implementation
- 17:09Functional core with calculator
- 19:40Pipeline orchestration
- 22:49Unified pipeline interface
- 26:21Result object intro
- 27:45Sequence component abstraction
- 29:09Transaction component abstraction
- 30:34Golden hammer benefits
related talks
28mNext Generation Ruby Web Appswith dry-rb, ROM, and Roda
36m"Business Logic in Ruby"
30mSOLID 101: A Review for Rubyists
28mWhat You See Is What It Does: A Structural Pattern for Legible Software
35mRails vs. Object Oriented Design
41mAPPLICATION ARCHITECTURE: BOUNDARIES, OBJECT ROLES, & PATTERNS
43mThe Tyranny of Structurelessness
27mSOLID in the Wild: Life When Your Software is Actually Soft