liveBook · Manning

REST

As explained in Pro ASP.NET Core 7, Tenth Edition

REST, or Representational State Transfer, is an architectural style for networked systems in which resources are identified and manipulated through representations and standardized operations.

REST, or Representational State Transfer, is the common architectural pattern for web services that return application data to clients. It has no authoritative specification, so implementations vary; the practical test is whether the service works for its projects. section 19.2

A REST API combines a URL with an HTTP method. The URL identifies the data object or objects, while the method describes the operation. Responses commonly contain JSON data consumed by clients such as JavaScript applications. section 19.2.1

Identifying a product

The URL /api/products/1 can identify the Product whose ProductId is 1. GET /api/products/1 conventionally retrieves it; another HTTP method changes the requested operation. section 19.2.1

How Pro ASP.NET Core 7, Tenth Edition covers it

How deep it goes
Defines the URL-and-method model and common verb conventions, but stops short of prescribing a complete REST specification.
Examples
Uses /api/products/1 to identify a product and GET, POST, PUT, PATCH, and DELETE to illustrate operations.
What it assumes
Assumes HTTP requests and responses, while introducing URLs, HTTP methods, JSON data, controllers, model binding, and validation.
What you can do after
Build RESTful endpoints by pairing URLs with HTTP methods and selecting controller or minimal-API implementations.
How it connects
Connects HTTP methods with URLs, JSON responses, controllers, MVC, model binding, and model validation.

Also explained in

Compare how 22 books explain REST →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Pro ASP.NET Core 7, Tenth Edition. The section links point to the parts of the book it draws on.