SQL vs NoSQL Databases: How to Choose
SQL vs NoSQL explained by data shape and access pattern, with concrete examples for relational, document, key-value, wide-column and graph databases.
Software Development
What is GraphQL?
Quick answer
A query language and runtime for APIs that lets clients request exactly the data they need in a single request.
GraphQL, explained
GraphQL was developed at Facebook and released publicly in 2015. Unlike a typical REST API, where each endpoint returns a fixed shape of data, GraphQL exposes a single endpoint and a schema describing all available data types. The client writes a query specifying exactly which fields it wants.
For example, a mobile app could ask for a user's name and the titles of their last five posts in one request, without receiving unneeded fields or making several calls. This reduces over-fetching and under-fetching. GraphQL also supports mutations for changing data and subscriptions for real-time updates. Trade-offs include more complex caching, the need to guard against expensive nested queries, and a steeper learning curve for small projects.
Related terms
API
Application Programming Interface: a defined set of rules that lets one piece of software request data or services from another.
QueryA request for data or information from a database, search engine, or other system, usually written in a specific language or format.
REST APIAn API that follows Representational State Transfer principles, using standard HTTP methods and URLs to work with resources.
Guides that mention GraphQL
Software Development
Trending
REST vs GraphQL: Differences and When to Use Each
REST vs GraphQL compared at the code level: how queries, caching, errors, security and tooling differ, and a clear framework for choosing on your next project.
Microservices vs Monolith: Which Architecture Should You Choose?
Microservices vs monolith explained plainly: why most teams should start with a modular monolith, the real costs of microservices, and the signals that justify splitting.