Brent Sordyl’s blog

If you insist on using the word “REST” in association with your API, ensure you:
* Use URIs to Identify Things, and ensure the URIs make sense independently of how those things may be accessed.
* Don’t bugger up standard protocols. You might think you have a better take on the authentication mouse trap, or an insight into how to make the Web transactional, but adding your own magic headers to HTTP and the chance is you’re adding state beyond the URI. Above all, don’t kill the bookmarking experience and testing with bog-standard, service-ignorant browsers.1
* Expecting people to follow meta-data, instructions or documentation given out of band, in particular which URIs to GET, POST, PUT, DELETE, to or the content to POST isn’t RESTful. It’s much better to return links to other representations, or forms to update and otherwise interact with a resource
(Link: REST :: What I Believe Roy Fielding Said)

Uncategorized architecture, restful

In this presentation filmed during QCon SF 2008, Aditya Agarwal is Director of Engineering at Facebook discusses Facebook’s architecture, more exactly the software stack used, presenting the advantages and disadvantages of its major components: LAMP (PHP, MySQL), Memcache, Thrift, Scribe.
(Link: Facebook architecture stack: Science and the Social Graph)

Uncategorized architecture, facebook, memcache, mysql, php, scalability