I would like to present the fruits many years’ labor trying to build a reusable set of components for building (web) applications really driven by Hypermedia.
The HATEOAS constraint boils down to a simple rule that the client cannot make assumptions about the resource representations and possible state transitions; all the necessary information should be provided by the server at run time. This poses a great obstacle when juxtaposed with the typical mindset, particularly that of designing Single-Page Applications. Single-Page Applications, or SPAs, are often built around rigid navigation structures (aka routing) and bespoke views and forms. Such approach to building software is a wasted opportunity for resilience to changes. The result is a set of bad practices such as code generation from API descriptions, and API versioning.
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.
Become a part of the world’s largest 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.