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.
High impact blog posts and eBooks on API business models, and tech advice
Connect with market leading platform creators at our events
Join a helpful community of API practitioners
Can't make it to the event? Signup to the Nordic APIs newsletter for quality content. High impact blog posts on API business models and tech advice.
Nordic APIs will use the information you provide on this form to provide updates and news.
You can change your mind at any time by unsubscribing from any email you receive from us or by contacting us at info@nordicapis.com. We will treat your information with respect. By clicking below, you agree that we process your information per the terms in our Privacy Policy.
We use Mailchimp as our marketing platform. By clicking below to subscribe, you acknowledge that your information will be transferred to Mailchimp for processing. Learn more about Mailchimp's privacy practices.
Become a part of our global community of API practitioners and enthusiasts. Share your insights on the blog, speak at an event or exhibit at our conferences and create new business relationships with decision makers and top influencers responsible for API solutions.
