The challenge with building fintech using a traditional REST-based protocol in banking as a service is the hundreds of transactions, accounts, users, and card objects that a REST-based protocol would fetch in the JSON. As a developer, you cannot specify which fields or objects you want - you have to pull the entire JSON and parse the data on your end which not only increases the load but the response times. This is especially critical today on any mobile app to lighten the payload and optimize for responsiveness.
It enforces a common schema
Developers building off REST APIs know there are common discrepancies in formats and schemas. GraphQL enforces a common schema. REST APIs can have one endpoint with one format and another endpoint with a slight variation. GraphQL is great for buffering against schema changes. Too many times, when developers add fields to a schema, it can break the existing implementation. One of the benefits of GraphQL is that it helps protect from such changes.
GraphQL powered by Productfy
To further our mission of enabling developers to build, deploy, and launch financial products to market in the easiest, fastest, and safest method, we decided to build upon our toolkit and post our interface to GitHub in order to contribute to ongoing efforts to get GraphQL into the hands of more developers who may find it more useful than REST for their application development.
Our GraphQL documentation tool is an ongoing project that we believe developers can iterate, enhance, and build more flexible fintech applications on.
- Left-hand tree structure for exploration of fields, objects, and arrays.
- Graphical query builder, with export in HTTP and CURL.
- Upcoming... more export languages and Postman collections
We welcome feedback on how we can improve on our documentation and interface.
Check out our repo and drop us a line!