Chris Wood Axway
GraphQL has emerged as a prominent talking point in the API landscape: its early success at Facebook, rapid adoption by other leading tech companies, and burgeoning open source community make it one of the most exciting new topics in our industry. But just as with any major milestone, GraphQL offers us a few practical questions to consider hand-in-hand with its advantages.
On one hand, overwhelmingly enthusiastic endorsements from highly respected developers and open source product vendors make GraphQL an easy train to hop aboard. On the other hand, these same figureheads have occasionally positioned GraphQL as an outright replacement for REST which may be cause for concern.
Curiously, traditional enterprise commentators like Gartner and Forrester haven’t yet shed much insight into GraphQL, and support from traditional API Management vendors is limited at best. GraphQL as an enterprise topic can therefore feel like a bit of a gray area. At Arvata our goal is to help you understand firstly why you might implement GraphQL, and secondly how you might approach this as part of your organization’s broader API strategy.
In this talk we’ll:
This post is older than 4 years. External links has been removed
October 10, 2017 12:40
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.