After a year that brought dozens of dates and thousands of attendees to our popular “Build your First Mobile App” training series, we’re happy to kick off 2014 with brand new content, built from your feedback, requests and the use-cases we have been powering for our customers. As usual, these trainings are 100% free (and all the software we use is free/open-source as well).
You can attend our new classes live for free, at the Kona Kai resort in San Diego Jan 7, 8 or 9 and start the year by building your first app, a high-performance app, or a great API! Check out this preview of the new content . . .
Analytics play a crucial role in ensuring the success of API programs. But analytics to glean insights and improve an API product don't happen by accident. Are you designing for analytics? I joined Brian Pagano & Kumar Srivastava of Apigee recently for a discussion of designing for analytics. The video is here as well as an excerpt and sneak preview of an article I'm finishing. The full story will be available on accenture.com in the coming weeks.
In our last post, we talked about pure REST and HATEOAS. In this post, we'll propose some ideas to initiate the creation of a new API design model based on pragmatic REST. We need to create an intellectual framework for API design that captures the spirit of how most popular web APIs are designed today.
In Part 1 of this discussion, we looked at questions people have in regard to HATEOAS. Now let’s examine how API crafters can revise their API so that it is truly RESTful. Because this is an introduction, we’ll avoid going into detail. Instead, we’ll assert the key point upfront: pure REST APIs require hypermedia clients.
Previously, we discussed HATEOAS (the hypermedia constraint) within the context of REST. This laid the groundwork for our discussion today, which is how to apply HATEOAS to an API strategy. Now, let’s look at some questions people have in regard to HATEOAS when setting up their API.
We recently discussed the six constraints of REST but today we'll deepen our discussion of hypermedia as the engine of application state or HATEOAS (hay-dee-ous), in an attempt to understand what HATEOAS really means.
Over the next several blog posts, we’d like to discover what hypermedia as the engine of application state, or HATEOAS (“Hay-dee-us”), means. We'll start by considering each of the six constraints of the architectural style of REST as defined by Roy Fielding in his PhD dissertation, with an emphasis on HATEOAS.