IT Glossary
What is GraphQL?
A query language for APIs through which an application asks for exactly the data it needs, in a single request.
Open a mobile app on a hotel wireless connection and watch a screen assemble itself slowly. Frequently the reason is that building that one screen required six separate calls to the server — customer, orders, addresses, loyalty status, recommendations, notifications — each waiting for the previous one, each returning far more fields than the screen displays. GraphQL was created at Facebook to end exactly that pattern. Instead of the server publishing fixed endpoints that return whatever their designer decided, it publishes a schema describing everything available, and the client sends a query naming precisely the fields it wants across as many related objects as it needs. One request goes out, one response comes back, containing nothing surplus. Two consequences follow that a buyer will notice. Mobile and slow-network performance improves in a way users perceive as the app feeling faster. And front-end teams stop queuing behind back-end teams for small changes, because adding a field to a screen no longer requires a new endpoint and a release. The trade is complexity on the server side, particularly around caching, cost control and preventing a single query from becoming expensive.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247
Why it matters for your business
Visibly faster mobile applications
One request carrying only the needed fields replaces several round trips, which is felt most on the poor connections real customers use.
New screens without server changes
Front-end teams compose the data they need from the existing schema, removing a dependency that used to add weeks to small changes.
One API for every consumer
Web, mobile and partner integrations query the same schema for different shapes of data, instead of each requiring bespoke endpoints.
Frequently asked questions
Does GraphQL replace REST?
Not generally, and treating it as a replacement causes most of the disappointment. REST remains simpler for straightforward resource access, caches beautifully at the network layer, and is what most partners expect to integrate with. GraphQL earns its keep where clients are varied and the data is deeply related — typically mobile apps and rich interfaces. Plenty of systems run both, deliberately.
Is GraphQL harder to secure than a conventional API?
It shifts the work rather than adding it. Because a client composes its own query, protection needs query depth and complexity limits, cost analysis, permissions enforced per field rather than per endpoint, and disabling schema introspection publicly. None of that is exotic, but it must be deliberate — a GraphQL endpoint left open with unlimited nesting is a denial-of-service vector anyone can trigger with a text editor.
What is a GraphQL schema?
A formal, typed description of every object, field and relationship the API exposes, published by the server and readable by tools. It functions as a contract: editors autocomplete against it, invalid queries are rejected before execution, and documentation generates itself. For a buyer it is a useful artefact to request during handover, because it describes the data model far more precisely than most written specifications.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247