No API integration solution is complete unless it stays current in supporting new developments in the API industry. GraphQL is the latest entrant to the API scene with, in my opinion, marginal improvements to the way Web-clients talk to the server. I have had the opportunity of speaking with some companies that are considering a move to GraphQL and the common thread across them was the caching feature that it offers. The lure of new technology was the second reason. While true, it is not totally correct because caching is a feature that is implementation driven and not dependent on any technology or framework.
This reminded me of when Angular JS framework was new to market and developers were attracted to it because it had two-way data binding. Two-way data binding is a simple feature which obviously was not unique to Angular.
Incremental improvements matter. Even if it not enabling a completely new thing, but even simplification of how a feature can be used or implemented, is important.
In due time, another incremental improvement introduced by another framework and specification may push GraphQL to the background, like Angular. But today GraphQL is an important technology. To customers who are toying with the GraphQL option, my advise is don’t ignore it. If you are starting a new project, GraphQL is a solid contender to be a part of your integration design. And if you are thinking of upgrading your existing application, a lot of other factors will come into play. For example, if caching is your main goal then there may be other ways of getting there. Look at your long term goals and weigh in how introducing GraphQL fits into your tech stack.
Of course, now that ZOAPI has full GraphQL support, you always have the option of building your server on ZOAPI, where the GraphQL/REST selection can be just a click. Your services can be generic and API layer agnostic – in fact the same services can be rendered using REST as well as GraphQL. Your existing ZOAPI (or otherwise) REST services can also be GraphQL enabled very easily.
ZOAPI preserves your investment in your applications by taking the technology variable out of the development.
Author: Manoj Agarwal, Chief Architect – ZOAPI.
Do not forget to visit the website: https://zoapiio.com.
