Architecture: The Next Generation
summary
Claim: Rails evolves from a monolith into a microservice ecosystem where teams mix a big Rails app with smaller services. Concrete stack examples include Rails + EmberJS + Sidekiq, plus AWS Lambdas, Docker/Compose, occasional Java or Python components. Historical moves that matter: Twitter rewrites search and migrates off Rails, Netflix builds fault injection via the Netflix Simian Army. Focus is on technical debt: what was built, what tools are used, and how reliably those pieces actually scale.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:21ARCHITECTURE THE NEXT GENERATION
- 2:34TECHNICAL DEBT. AND HOW ARCHITECTURE CAN CREATE OR RELIEVE IT
- 2:47ARCHITECTURE IS THE ROOT OF A LOT OF OUR TECHNICAL DEBT
- 4:48RAILS TOOK THE WEB DEVELOPMENT PROCESS AND REFACTORED IT. RAILSCONF
- 5:01WHAT KIND OF REFACTOR IS RAILS?
- 8:56Misunderstanding Rails Queries - The N+1 Problem Misunderstanding Ruby's API Common code smells
- 10:19IS RAILS FINISHED?
- 12:59NETFLIX'S SIMIAN ARMY
- 14:06EVERY ARCHITECTURE IS A BRAVE NEW WORLD!
- 14:34MONOLITHIC DESIGN
- 16:15MONOLITHS ARE ROOTED IN UNIFORMITY
- 19:48MICROSERVICE S ARE ROOTED IN MODULARITY
- 20:56ECOSYSTEMS ARE ROOTED IN MODULARITY
- 23:44FIRST, KILL THE HYPE.
- 26:00KNOWLEDGE IS POWER
- 33:30WHAT IS COMING FOR US NEXT?
related talks
56mFrom Homogeneous Monolith to Heterogeneous Microservices Architecture
42mHow Rails fosters a diverse and competitive tech ecosystem in the era of big tech
40mService Architectures for Mere Mortals
33mServices and Rails: The Sh*t They Don't Tell You
27mScaling a Rails Monolith w/Event Driven Microservices
32mRefactoring Legacy Apps with APIs and Messages
33mServices and Rails: The Shit They Don't Tell You
28mServices and Rails: The Shit They Don't Tell You