Rails as an SOA Client
summary
Rails apps become service-front ends so the team builds bounded integration tests that replace real services with fakes and adds contract tests (consumer-driven contracts via RSpec or tools like pacto/pact) to pin down who breaks the API. Service gateways use Faraday (Rack-like middleware) to centralize JSON/XML serialization, caching and logging; an HTTP caching middleware relying on HTTP caching headers cuts network calls and lets product teams control freshness without redeploys.
AI-written summary · about
chapters (6)
- 0:00Start
- 11:48OUT-OF-PROCESS
- 17:34BOUNDED INTEGRATION TESTS
- 20:29rack
- 22:07faraday
- 24:11service gateways
related talks
23mAbstracting a Service - A Case Study in Forward Thinking with SOA
43mRails services in the walled garden
34mSOA and the Monolithic Rails App Anti-Pattern
34mService Oriented Architecture at Square
30mService Oriented Design in Practice
22mNitty Gritty Service Building
28mNitty Gritty Service Building
40mService Architectures for Mere Mortals
