Rubyonrails. Brian McCallister - Shedding. Shedding Shedding is a technique Paul, John, and I hashed out (during the recent ApacheCon hackathon) for service lookup in pure HTTP.
The problem it tries to solve is resolving where to make a request to if you have a URL, say which is a backend service for managing session state in Hypothetical Incorporated. With shedding you set up DNS to send all traffic on the .service. domain to a set of shed servers. The shed servers serve up HTTP and respond to all requests with a 302 to the correct location, so our request above would look like: --- Request --- --- Response --- POST /session HTTP/1.1 Host: storage.service Content-Length: 0 HTTP/1.x 302 Moved Location: POST /session HTTP/1.1 Host: 10.0.1.5 Content-length: 0 HTTP/1.x 201 Created Location: Content-length: 0.
SOA, REST, ESB, hub and spoke, good, evil, etc. I'm currently in the midst of the last week of a sort of a "working holiday".
I've been home, sleeping as long as I like and working more or less when I feel like it. I've also had the freedom to concentrate on the things that interest me, rather than, say, the things that the everyday demands of the job might have forced upon me. One immediately obvious consequence of those arrangements has been a spike of activity on this blog -- I've blogged as much in the last three weeks as in the entire 12 months prior. ;) Another consequence has been an enormous increase in the quality of my work environment -- rather than a moldy old open plan office, I'm working from my terrace at home, enjoying the fresh air and a spectacular view of the Rhein river valley. Twitter nanoformats » home.