SOA and the Monolithic Rails App Anti-Pattern
summary
A monolithic Rails app that handled lead generation gets incrementally strangled into a service-oriented system: the codebase splits into focused services like lead-qualification service, delivery workers via a message queue, and a separate reporting store. The team extracts business rules behind RSpec scaffolding, moves delivery to asynchronous JSON messages (Resque-style) so parallel workers improve responsiveness, toggles new behavior per school via a DB flag, uses a small DSL and Couch caching for shared data, and warns that distributed testing, deployments and failure handling become the new complexity.
AI-written summary · about
chapters (5)
- 0:00Start
- 6:41Separate Responsibilities
- 20:10Maintainability
- 21:37Testability
- 23:26Overly Decomposed Services
related talks
40mFacing the Monolith Overcoming Monolithic Applications with SOA
23mAbstracting a Service - A Case Study in Forward Thinking with SOA
40mMonoliths Between Microservices
29mSmash the Monolith: Refactoring into SOAs
37mRails as an SOA Client
21mTaming Monoliths Without Microservices
36mAn Iterative Approach to Service Oriented Architecture
27mScaling a Rails Monolith w/Event Driven Microservices