liveBook · Manning

REST maturity model

As explained in Microservices Patterns, Second Edition

The REST maturity model classifies HTTP APIs by their progression from a single endpoint toward resource orientation, HTTP verbs, and hypermedia controls.

The REST maturity model classifies HTTP APIs by how they use endpoints, resources, HTTP verbs, and hypermedia controls. Its four levels describe increasing use of these REST mechanisms. section 8.2.2

The levels distinguish these API design choices:

  • Level 0 uses one URL endpoint, with each POST request specifying an action, target, and parameters. section 8.2.2
  • Level 1 introduces resources, though clients still use POST to specify actions. section 8.2.2
  • Level 2 uses HTTP verbs such as GET, POST, and PUT to retrieve, create, and update resources. section 8.2.2
  • Level 3 uses HATEOAS: resource representations contain links for actions, reducing the need to hard-wire URLs into clients. section 8.2.2

Order service

A POST /orders endpoint creates an order, while GET /orders/{orderId} retrieves one. A level 3 representation could include a link for cancelling that order. section 8.2.2

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines four levels and illustrates them with endpoint, verb, and hypermedia examples.
Examples
Uses order creation and retrieval endpoints, plus an order-cancellation link, as examples.
What you can do after
Evaluate an HTTP API's maturity by checking its endpoints, resource use, verbs, and hypermedia links.
How it connects
Connects REST to HTTP APIs, resources, HTTP methods, and HATEOAS.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.