This post originated from an RSS feed registered with Web Buzz
by Mark Masterson.
Original Post: Why Multi-Core is Easy and Internet is Hard | Lambda the Ultimate
Feed Title: Process Perfection
Feed URL: http://www.jroller.com/MasterMark/feed/entries/rss
Feed Description: Life, the Universe, workflow, BPM, Java, Ruby, functional/generative/meta programming, pi calculus, patterns, the Grid, agents, software architecture and the kitchen sink. :)
REST proponents would say that programming systems like the Internet is just sociological problem, as the technical problems are all solved by REST. I'm not far from believing in it myself, it's hard to see what is hard about loosely coupled distributed systems that can't be solved using it.
Not sure what's hard to believe. A REST-ful URI is just a lambda name! If you then maintain memory-safety, you now have a secure, distributed lambda calculus.
Besides URIs we have other defining traits in REST (e.g. HATEOAS, uniform interface), some of which aren't well mapped to well known theories. Also nothing says that a distributed lambda calculus is a good fit to distributed systems when compared to distributed Pi or Join.
The actual comment was believing that it's just a sociological problem. IMHO there's some issues that are still open (e.g. service versioning, authentication) and need some engineering work. Don't get me wrong, I've been working solely with REST based architectures this year and I'm not looking back to anything else (to work within the Internet).
Go get more at the link above. The chart alone is worth the price of admission.
This is all so bloody obvious. But as a long time fan of zombie flicks, the tenacity of the undead never fails to surprise me.
Previous Topic
