Rails services in the walled garden
summary
Built a suite of nine+ Rails services that integrate over HTTP and XML to automate data centers, handling roughly 30,000 requests/hour on a single service. The team uses OAuth2 for stateless auth, replaces ActiveResource where it blocks headers or caching, adds a box_pagination extension for collection metadata, and avoids sharing writable databases by creating read-only local caches updated via events or a message bus like RabbitMQ. The approach proves workable with careful caching, pagination, and centralized tooling.
AI-written summary · about
chapters (10)
- 0:00Start
- 3:08Advantages of Using Soa versus Building a Monolithic Application
- 5:08Disadvantages of Building Service Oriented Architecture
- 6:15Continuous Integration
- 10:23Authentication
- 14:15Authorization
- 20:08Pagination
- 21:03Http Headers
- 27:44Callback Uris
- 32:10Guidelines
related talks
33mServices and Rails: The Sh*t They Don't Tell You
23mAbstracting a Service - A Case Study in Forward Thinking with SOA
37mRails as an SOA Client
33mServices and Rails: The Shit They Don't Tell You
34mService Oriented Architecture at Square
20mSafely Decomposing a Highly Available Rails App
40mService Architectures for Mere Mortals
33mAdventures with Micro Services in Rails
