The Clean Architecture: How to Grow From Startup to Enterprise
summary
Shows a rails-first, monolith‑first then split path: keep business code in domain folders under apps/, use Trailblazer operations + Reform for use cases and factories, ActiveRecord-based entities/aggregators behind repository adapters, heavy unit tests, and ActiveAdmin as a separate Rails app. When teams grow, physically split apps and talk over gRPC protos (generated clients/controllers). Deployment is automated with Chef; claim is faster features and safe evolution toward microservices, with working prototypes in production.
AI-written summary · about
chapters (8)
- 0:00Problem statement
- 1:22Architectural approach
- 5:32Clean architecture principles
- 9:23Design patterns and tools
- 12:29Structure and domains
- 19:43Application infrastructure
- 25:57Microservices and gRPC
- 34:29Q&A session
