APPLICATION ARCHITECTURE: BOUNDARIES, OBJECT ROLES, & PATTERNS
summary
Argues Ruby culture lacks clear application architecture and shows concrete fixes: models split into forms for input coercion, validators for complex rules, and repositories as a one‑way boundary to the data layer. Describes a JSON API for an iOS photo‑sharing app built with use cases and ports‑and‑adapters style, uses in‑memory repository implementations to get fast tests, and offers a chassis gem with a repository module as a reusable starting point while warning about Rails’ tendency to entangle concerns.
AI-written summary · about
chapters (11)
- 0:00Introduction and context
- 2:20Rethinking application design
- 5:09Core application components
- 7:30Boundaries and layers
- 9:42Domain objects and persistence
- 13:28The repository pattern
- 16:29Implementation of use cases
- 20:42Delivery mechanisms
- 23:31Testing and composition
- 26:52Recommendations and resources
- 29:56Q&A session
related talks
39mFunctional Architecture for the Practical Rubyist- 39mFunctional Architecture for the Practical Rubyist
41m"Tackling complex architecture in Ruby"
35mBuild Complex Domains in Rails
32mComponent-based Architectures in Ruby and Rails
22mBuilding the Great Wall: API Driven Applications
51mThe Ruby Box
45mThe illusion of stable APIs