Many developers mock RPC-interfaces, SOAP and the like. Instead they go on to build “RESTful” HTTP interfaces using descriptive URLs and HTTP verbs to standardize actions. They document their URLs and the actions that can be taken on each of them as their API. Finally they build applications consuming these interfaces based on the API spec. The above is *not* REST. It’s RPC all over again.

What everyone forgets is the design principle of “hypermedia as the engine of application state”. This talk will attempt to shed some light on this principle and share a few ideas for working with it in practice.