Service Oriented Design in Practice
summary
Service oriented design with Ruby reduces coupling but introduces hidden costs: five developers run a front end plus three services, drop RabbitMQ when it adds opacity, and fold one service back into the main app to simplify dependencies. Operational fixes include a hocl private gem to start everything locally, a u20box tool to introspect requests and host health, client libraries tested against services with Artifice rack activation, layered tests (unit, integration, UI) and transaction ID tracing to follow cross-service requests. Continuous small fixes and proportional investment guide decisions.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:01Service Oriented Design
- 1:47Lewis Brandi Quote
- 3:16Thesis
- 5:03TT Plano
- 6:47Isolation
- 9:00Operability
- 10:13First Service
- 11:27hocl
- 12:10copy and paste
- 13:06deploy scripts
- 14:26problems at home
- 14:42rubygems
- 15:57Services
- 20:12Testing the Client
- 21:45Testing the App
- 23:34The Testing Period
- 24:22The Testing Pyramid
- 25:03Continuous Improvement
- 25:19Root Cause Analysis
- 25:34Proportional Investment
- 26:30Development is Production
- 27:04Hidden Costs
related talks
36mAn Iterative Approach to Service Oriented Architecture
23mAbstracting a Service - A Case Study in Forward Thinking with SOA
34mService Oriented Architecture at Square
40mService Architectures for Mere Mortals
26mService Oriented Disasters
37mRails as an SOA Client
01h 00mService Oriented Architecture for Robust & Scalable Systems
54mServices, Services, Everywhere!