I Got 99 Problems, but REST Ain’t One
RWX / CDX
Fort Lauderdale · November 27 - 30, 2012
About this Presentation
The world’s most popular services expose ReST APIs. Whether it’s in Google, Twitter, Amazon, or even your middleware, ReST is everywhere. Have you ever wondered why APIs look the way they do? Is there a balance between API design for usability and scale, or can we have them both? What’s the relationship between standards such as WS-* and ReST?
This session walks you through the relationship between the ReST API and architecture. It dissects popular APIs from companies such as Amazon and Twitter and uncovers designs that facilitate scale. Along the way, the presentation identifies aspects that can be cherry-picked, versus those that work best together. It also underscores trade-offs you should know about when putting together your API.

Cloud Engineer at Twitter
Adrian is an active member of cloud interoperability, REST, and DevOps circles. He is the founder of a few popular open source projects, notably Apache jclouds and Netflix denominator, both of which java libraries that help create portable cloud deployments. Adrian maintains the http/2 implementation of Square okhttp. Adrian's currently focused on cloud computing at Twitter.