Joakim Lundborg Wrapp
The status quo of the RESTful API as the state of the art of API design is being challenged, at least for app development. GraphQL and similar technologies are trying to address some perceived problems in REST, and by extension HTTP itself. What are they trying to do, and what will happen if they succeed?
Based on experience using GraphQL with a sprawling microservice system, this talk focuses on why this is happening, and what will happen as we transition into a more declarative and graph-oriented ways of defining APIs. What does this mean for open data and the open web? How can we ensure long-term stability of APIs in this new paradigm?
This post is older than 4 years. External links has been removed
October 26, 2016 13:00
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.