Building Distributed Applications
summary
Company moves from one monolithic Rails app to many smaller apps to reduce load and speed releases, running light services like registration on 2–3 mongrels while pushing a heavy rating engine to its own boxes; uses DRb for remote objects, adds a Rinda ring server for discovery, and solves class-transfer with include DRBUndumped. Mac framework 0.8.1 registers shared routes, views and objects; proxies work but marshaling hundreds of records causes noticeable slowdown and migrations/portlets require careful naming.
AI-written summary · about
chapters (16)
- 0:00Start
- 1:03Distributed Programming
- 1:22Why Distributed Programming
- 1:53Scalability
- 5:34Logging Server
- 11:24Proxies
- 12:00Hello Method
- 16:29Views and Layouts with Multiple Applications
- 18:18Add the Mac Distributed Package
- 28:07Render Url
- 28:56Porting the Mac Distributed Package to Other Frameworks like Rails and Merb
- 31:56Run Multiple Ring Servers
- 34:12How Do You Deal with a Lazy Loading of Objects
- 37:14Migrations and Portlets and Distributed Applications
- 38:41Notifications
- 42:56Any Issues with Jruby
related talks
26mRuby off the Rails: Building a distributed system in Ruby
16mOne Ruby App to Rule Them All
43mRails is a Follower
28mSplitting Your App
33mFar and Away (A Tour of DistribRuted Programming with Ruby)
34mService Oriented Architecture at Square
43mRails services in the walled garden
01h 09mRails 3 ...and the real secret to high productivity
