Facing the Monolith Overcoming Monolithic Applications with SOA
summary
A monolithic lead-generation app is split into narrow, focused services and the claim is that doing so cuts maintenance cost and lets the system scale horizontally. Implementation details: front-end and back-end services, lead generation platform for storing leads, synchronous calls over Sinatra + JSON + HTTP, asynchronous work via beanstalk queue (Resque/Redis mentioned), authentication issues solved with token responses and shared gems for API clients. Testing needs full staging/acceptance runs; security uses SSL API keys and IP whitelisting.
AI-written summary · about
chapters (18)
- 0:00Start
- 0:52Charles Max Wood
- 1:59How it Starts...
- 3:16How it Fails...
- 3:45How We Started...
- 6:45Your Backlog
- 9:25Communication
- 11:29HTTP
- 13:22Organization
- 14:19Resque
- 15:21Queuing
- 17:16JSON Feed
- 17:46Feeds
- 18:14Front End Services
- 20:35A Few Notes...
- 21:38Naming Services
- 22:48Security
- 24:50Online Training
related talks
34mSOA and the Monolithic Rails App Anti-Pattern
30mMonolith-ifying perfectly good microservices
23mAbstracting a Service - A Case Study in Forward Thinking with SOA
29mSmash the Monolith: Refactoring into SOAs
56mFrom Homogeneous Monolith to Heterogeneous Microservices Architecture
23mMicroservices within a Monolith
27mScaling a Rails Monolith w/Event Driven Microservices
36mDo Proper Monoliths before You Do Microservices!