tag:blogger.com,1999:blog-3718956085911858962.post643850874231885910..comments2023-12-27T14:48:02.113+05:30Comments on Electric Sheep Blog: Two stage resource oriented web application architecturesAnonymoushttp://www.blogger.com/profile/11938300811286150164noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-3718956085911858962.post-30681159331571720302008-10-31T18:57:00.000+05:302008-10-31T18:57:00.000+05:30Hi Sidu,A few points I'd disagree with:1. REST isn...Hi Sidu,<BR/><BR/>A few points I'd disagree with:<BR/><BR/>1. REST isn't CRUD. CRUD is CRUD and you can do both with HTTP. (As an aside my new book has a separate chapter on CRUD because of this)<BR/><BR/>2. The case for ROA isn't simple at all, and most HTTP services are just as RPC as SOAP services today. <BR/><BR/>3. Enterprises shouldn't break up there services into tiny services arbitrarily because you lose cohesion. Services should be as small as possible, but no smaller.<BR/><BR/>4. HTML and JSON are simply formats. The Web doesn't care, and HTTP allows clients to negotiate (the accept header). So there's no real disconnect between a browser wanting HTML and a program wanting YAML.<BR/><BR/>5. Performance is application specific, but if you design your resource landscape well, and you grok caching then you've got a fighting chance of making it work.<BR/><BR/>JimAnonymousnoreply@blogger.com