13 Hateoas Vs Graphql

title: HATEOAS vs GraphQL — Comparing API Design Approaches weight: 23 date: 2026-06-28 lastmod: 2026-06-28 description: Compare HATEOAS and GraphQL API approaches including discovery, evolvability, performance, client requirements, and when to choose each based on use case. tags: [api-development, hateoas]

HATEOAS and GraphQL represent different API philosophies. HATEOAS uses server-driven discovery with hypermedia links. GraphQL uses client-driven queries for precise data fetching. Each excels in different scenarios.

```mermaid
flowchart TD
  A[API Design] --> B[HATEOAS]
  A --> C[GraphQL]
  B --> D[Server-driven discovery]
  B --> E[Evolvable URLs]
  B --> F[Progressive web apps]
  C --> G[Client-driven queries]
  C --> H[Precise data fetching]
  C --> I[Complex dashboards]
  style A fill:#e1f5fe
  style B fill:#c8e6c9
  style C fill:#fff9c4

HATEOAS: Server controls navigation via links. Clients follow rel semantics. Excellent for evolvability and discoverability. Best for public APIs where clients need guidance. GraphQL: Clients specify exact data needs in queries. Single endpoint. Best for complex UIs needing flexible data combinations.

What's Next

Now learn about tools and frameworks in Hypermedia APIs and HATEOAS.