Nexonoma Compare · Curated snapshot

API Style

Categorization of design and architectural principles for interfaces (e.g., REST, GraphQL, gRPC) to guide modeling, communication, and error handling.

Compare concrete tools against the same functional, non-functional, and commercial properties. The matrix presents evidenced differences. Weighting, recommendations, and selection will follow in Decide.

Catalog Explorer Decide with these candidates

Candidates

Select 2 to 4

Candidates	Representational State Transfer (REST) Observed on 2026-08-25	GraphQL Observed on 2026-08-25	gRPC Observed on 2026-08-25
Functional
Interaction modelCore abstraction through which a client interacts with the API.	Resource-oriented REST identifies resources and manipulates them through representations within a uniform interface. 1	Query-oriented Clients express data requirements as a GraphQL document and select fields from a typed schema. 4 5	Service / RPC-oriented A service defines remotely callable methods with parameters and return types. 9
Contract modelForm and binding nature of the machine-readable interface definition.	Optionally formalized REST does not mandate an IDL; OpenAPI can describe HTTP interfaces in a machine-readable form. 1 3	Schema required Every GraphQL service defines types and fields against which incoming operations are validated and executed. 5	Proto-first gRPC uses Protocol Buffers by default as the IDL for services and messages; other alternatives are possible. 9
OperationsCore building blocks for read, write, and continuous interactions.	RessourcenRepräsentationenHypermedia The uniform interface combines resource identification, representations, self-descriptive messages, and hypermedia. 1	QueryMutationSubscription Queries are required; mutations and subscriptions can be exposed as additional root operations. 4 5	UnaryServer-StreamClient-StreamBidirektional gRPC defines four method types ranging from simple request/response to independent bidirectional streams. 9
Transport profileTypical transport foundation for requests, responses, and streams.	Web / HTTP REST is an architectural style for distributed hypermedia systems and is typically implemented over HTTP for web APIs. 1 3	Usually HTTP The GraphQL specification is transport-agnostic; HTTP is the most common transport for queries and mutations. 6	HTTP/2 gRPC maps RPCs onto HTTP/2 streams and uses multiplexing and long-lived connections. 8 10
StreamingHow continuous or multi-part data flows are modeled.	Separate pattern The REST constraints do not define a dedicated streaming operation; continuous connections are modeled through additional web mechanisms. 1	Subscriptions A subscription creates a response stream from an underlying event stream; support is optional. 4	Native RPC streams Server, client, and bidirectional streaming are first-class types in the service contract. 9
Architecture & operations
Payload modelTypical form and structure of transferred payload data.	Media-type dependent Resource state is transferred as a representation whose concrete format is determined by media type and application. 1	JSON over HTTP GraphQL over HTTP commonly uses JSON for requests and structured responses with data, errors, and extensions. 6	Protobuf by default Protocol Buffers describe the service interface and messages by default; generated clients serialize payloads. 9
Browser accessTechnical path through which browser clients can use the API.	Direct Browsers can call HTTP-based REST interfaces directly through existing web APIs. 1 3	Direct Browsers send queries and mutations via GET or POST to a typical single HTTP endpoint. 6	gRPC-Web + proxy Browsers use gRPC-Web and typically a proxy such as Envoy to translate requests to the gRPC backend. 11
Caching modelMechanism used to cache reusable responses and data.	HTTP-native REST includes a cache constraint; HTTP defines standardized cache keys, directives, and reuse rules. 1 2	GET + client cache GET can enable HTTP or CDN caching; GraphQL clients also commonly normalize data through global object IDs. 6 7	Application-managed The gRPC core documentation describes RPC calls and streams; reusable application results are cached outside this transport model. 9
Architecture profileNeutral core trade-off between generality, client flexibility, and efficiency.	The uniform interface improves visibility, simplicity, and independent evolution. Its generality can cost efficiency compared with specialized interfaces.1	Clients gain a flexible, typed selection of required fields. The shared graph and its resolvers move additional modeling and operational responsibility into the GraphQL service.5 6	The explicit service contract enables efficient polyglot communication and native streaming. Code generation, HTTP/2 connections, and browser proxies increase infrastructure coupling.8 9 11
Ecosystem & standardization
Definition formForm in which the approach is standardized and evolved.	Architectural style REST is defined as a set of architectural constraints for distributed hypermedia systems. 1	Open specification The formal GraphQL specification defines the language, type system, validation, and execution independently of an implementation. 4	Open-source framework gRPC is an open RPC framework with multiple language implementations and a shared protocol model. 8
Tooling entryPrimary anchor for documentation, validation, and client support.	HTTP + optional OpenAPI HTTP tooling works directly; OpenAPI can add a language-agnostic, machine-readable contract when needed. 3	Schema + introspection The schema fully describes available data and anchors validation, documentation, and code tooling. 5 4	IDL + generated stubs Compiler plugins generate client and server code for supported languages from the service definition. 9

Representational State Transfer (REST)

REST is an architectural style that defines the communication between client and server via the HTTP protocol.

Functional

Interaction model: Resource-oriented
REST identifies resources and manipulates them through representations within a uniform interface.
1
Contract model: Optionally formalized
REST does not mandate an IDL; OpenAPI can describe HTTP interfaces in a machine-readable form.
1 3
Operations: RessourcenRepräsentationenHypermedia
The uniform interface combines resource identification, representations, self-descriptive messages, and hypermedia.
1
Transport profile: Web / HTTP
REST is an architectural style for distributed hypermedia systems and is typically implemented over HTTP for web APIs.
1 3
Streaming: Separate pattern
The REST constraints do not define a dedicated streaming operation; continuous connections are modeled through additional web mechanisms.
1

Architecture & operations

Payload model: Media-type dependent
Resource state is transferred as a representation whose concrete format is determined by media type and application.
1
Browser access: Direct
Browsers can call HTTP-based REST interfaces directly through existing web APIs.
1 3
Caching model: HTTP-native
REST includes a cache constraint; HTTP defines standardized cache keys, directives, and reuse rules.
1 2
Architecture profile: The uniform interface improves visibility, simplicity, and independent evolution. Its generality can cost efficiency compared with specialized interfaces.1

Ecosystem & standardization

Definition form: Architectural style
REST is defined as a set of architectural constraints for distributed hypermedia systems.
1
Tooling entry: HTTP + optional OpenAPI
HTTP tooling works directly; OpenAPI can add a language-agnostic, machine-readable contract when needed.
3

GraphQL

GraphQL is a query language for APIs and a runtime for executing those queries.

Functional

Interaction model: Query-oriented
Clients express data requirements as a GraphQL document and select fields from a typed schema.
4 5
Contract model: Schema required
Every GraphQL service defines types and fields against which incoming operations are validated and executed.
5
Operations: QueryMutationSubscription
Queries are required; mutations and subscriptions can be exposed as additional root operations.
4 5
Transport profile: Usually HTTP
The GraphQL specification is transport-agnostic; HTTP is the most common transport for queries and mutations.
6
Streaming: Subscriptions
A subscription creates a response stream from an underlying event stream; support is optional.
4

Architecture & operations

Payload model: JSON over HTTP
GraphQL over HTTP commonly uses JSON for requests and structured responses with data, errors, and extensions.
6
Browser access: Direct
Browsers send queries and mutations via GET or POST to a typical single HTTP endpoint.
6
Caching model: GET + client cache
GET can enable HTTP or CDN caching; GraphQL clients also commonly normalize data through global object IDs.
6 7
Architecture profile: Clients gain a flexible, typed selection of required fields. The shared graph and its resolvers move additional modeling and operational responsibility into the GraphQL service.5 6

Ecosystem & standardization

Definition form: Open specification
The formal GraphQL specification defines the language, type system, validation, and execution independently of an implementation.
4
Tooling entry: Schema + introspection
The schema fully describes available data and anchors validation, documentation, and code tooling.
5 4

gRPC

gRPC is a powerful RPC framework from Google that efficiently provides remote procedure capabilities.

Functional

Interaction model: Service / RPC-oriented
A service defines remotely callable methods with parameters and return types.
9
Contract model: Proto-first
gRPC uses Protocol Buffers by default as the IDL for services and messages; other alternatives are possible.
9
Operations: UnaryServer-StreamClient-StreamBidirektional
gRPC defines four method types ranging from simple request/response to independent bidirectional streams.
9
Transport profile: HTTP/2
gRPC maps RPCs onto HTTP/2 streams and uses multiplexing and long-lived connections.
8 10
Streaming: Native RPC streams
Server, client, and bidirectional streaming are first-class types in the service contract.
9

Architecture & operations

Payload model: Protobuf by default
Protocol Buffers describe the service interface and messages by default; generated clients serialize payloads.
9
Browser access: gRPC-Web + proxy
Browsers use gRPC-Web and typically a proxy such as Envoy to translate requests to the gRPC backend.
11
Caching model: Application-managed
The gRPC core documentation describes RPC calls and streams; reusable application results are cached outside this transport model.
9
Architecture profile: The explicit service contract enables efficient polyglot communication and native streaming. Code generation, HTTP/2 connections, and browser proxies increase infrastructure coupling.8 9 11

Ecosystem & standardization

Definition form: Open-source framework
gRPC is an open RPC framework with multiple language implementations and a shared protocol model.
8
Tooling entry: IDL + generated stubs
Compiler plugins generate client and server code for supported languages from the service definition.
9

Sources

Numbers link each property to its evidence.