liveBook · Manning

REST

As explained in Microservices Patterns, Second Edition

An architectural style for networked systems defined by constraints on interactions between components and resources.

REST is an architectural style for interprocess communication, usually over HTTP. Its constraints emphasize scalable interactions, general interfaces, independent deployment, and intermediaries. APIs model business objects or collections as resources identified by URLs. section 8.2.2

Clients manipulate resources using HTTP verbs:

Order service

POST /orders creates an Order; GET /orders/{orderId} retrieves one. An HTTP-based API is not necessarily RESTful: a maturity model distinguishes services that use a single action endpoint from those that support resources. section 8.2.2

Figure 8.5 An OpenAPI document describes a REST APIs endpoints including URL paths, HTTP methods, request and response bodies, and so on.
rest open api doc

An OpenAPI document can describe endpoint paths, HTTP methods, and request and response bodies. section 8.2.2

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines resources, URLs, representations, and HTTP verbs, and introduces a REST maturity model.
Examples
Uses Order creation and retrieval endpoints to illustrate resource operations.
What you can do after
Apply REST by modeling business objects as resources and mapping retrieval, creation, and updates to HTTP requests.
How it connects
Connects REST to HTTP, resources, microservice communication, and the Richardson Maturity Model.

Also explained in

Compare how 30 books explain REST →

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.