I Got 99 Problems, but REST Ain't One

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.

Copyright © 2013 Oracle and/or its affiliates. Oracle® is a registered trademark of Oracle and/or its affiliates. All rights reserved. Oracle disclaims any warranties or representations as to the accuracy or completeness of this recording, demonstration, and/or written materials (the "Materials"). The Materials are provided "as is" without any warranty of any kind, either express or implied, including without limitation warranties of merchantability, fitness for a particular purpose, and non-infringement.