Surrounded by Microservices

on YouTube ↗28m

" summary

Netflix Studio becomes a suite of 50+ apps after decomposing a Rails monolith that once had ~30 developers and >300 DB tables, and the architecture centers on hexagonal architecture to keep business logic independent of persistence. Entities use dry-struct, repositories wrap swappable data sources (ActiveRecord, REST, gRPC) and interactors use the interactor gem with dependency injection so unit tests mock repositories while integration tests use VCR and generated clients from swagger code generator. Alerts trigger at ~20% downstream failure; the approach works and delays big infrastructure choices.

AI-written summary · about

" chapters (17)

1. 0:00Start
2. 5:52The Active Record Pattern
3. 6:43Persistence Layer
4. 8:11Core Concepts
5. 8:44Repositories
6. 8:56Data Sources
7. 9:23Interactors
8. 9:51Entities
9. 16:08Errors
10. 16:45Graceful Failure
11. 18:24Alarm Fatigue
12. 19:54Alternatives
13. 23:23Purpose of Good Architecture Is To Delay Decisions
14. 24:05Testing Strategy
15. 24:33Rails Testing Look like
16. 25:58Integration Specs
17. 26:58Conclusion

" related talks

• 40mMonoliths Between MicroservicesVladimir Dementyev · RailsConf 2020 CE
• 26mMonolith-ifying perfectly good microservicesBrian Scanlan · LDX3 London 2025
• 30mMonolith-ifying perfectly good microservicesBrian Scalan · Rails World 2023
• 27mScaling a Rails Monolith w/Event Driven MicroservicesMarko Anastasov · WindyCityRails 2016
• 23mClient/Server Architecture: Past, Present, & FutureMike Groseclose · RailsConf 2016
• 21mTaming Monoliths Without MicroservicesKelly Sutton · RubyConf AU 2019
• 32mRefactoring Legacy Apps with APIs and MessagesCorey Ehmke · LoneStarRuby Conf 2013
• 23mAbstracting a Service - A Case Study in Forward Thinking with SOAStuart Corbishley · Rubyfuza 2013