# What GraphQL means for your Business
If you are a techpreneur who is not a developer, chances are that you don’t know about developer tools and processes, and this can cause you to suffer from wrong decision making. In today’s world, you should strive to have basic knowledge about developer tools because one way or the other, it affects the product and customer engagement.
Recently, big companies like Facebook, GitHub, Shopify, and Atlassian have been switching and adopting GraphQL; even Twitter recently joined the GraphQL party. And I’m sure you must be wondering what GraphQL is and how it can possibly affect your business.
# What is GraphQL?
GraphQL is a query language for your API, and a server-side runtime for executing queries by using a type system you define for your data. - GraphQL
Okay, that definition might be a little too technical for a business man, so here’s a much simpler definition. "GraphQL is a language for querying backend systems from an application that is more robust and lean than conventional APIs, but much simpler and safer than directly interacting with the database via SQL" Echobind.
If you have a backend engineer in your company, chances are that his work is to create API's—sometimes REST or SOAP—which he/she makes available for your front end developer or mobile app developer. Now GraphQL is query language built to make products more usable and performant with the extra benefit of reduced deployment and hosting costs.
Before the advent of GraphQL, REST API (probably what your business is built on) was the prominent choice. This architecture cost businesses more because for every request, there had to be a call with the server, and each call cost money for the businesses, and time for the customer, but GraphQL solves that issue to a large extent.
# Why business needs GraphQL?
It is very fast: This means faster development time, faster load times on any request from the customer (if need be), and fast deployment. Unlike REST API, every request is a load on the server, so imagine you were a customer who wanted to search for a product, on click of the search button, you’re making a new request to the server, and then you wait for a response. Every time you click on a specific product, another request is sent to the server. This increases the time it’ll take for the customer to make their buying decision, and this might lead to a high bounce rate for your site, which is not something you want at all. GraphQL solves this issue by making your product faster for users.
Faster Development and Iteration: The way products were developed before GraphQL, the backend guy wrote the API and documents, then the Frontend guy used the documentation to consume the API. Sometimes, if there were issues with the API, and the frontend guy needed to make modification, he had to wait till the backend developer attended to his situation. This way of doing things takes time, especially in big organizations where the front-end developer doesn’t have easy access to the backend team. Although GraphQL doesn’t solve the issue entirely but it reduces it, as the frontend developer has access to query all data made available by the Backend guy.
- Easy Adoption: GraphQL can be easily adopted with REST, making for easier adoption by backend engineers and front end developers.