REST is a difficult topic. A lot of different opinions and misunderstandings. So I will add my own opinionated view and try to explain my reasons on the way. In this tutorial I will build a nice little REST API step by step.

Our domain will be a robot factory. It has several blueprints for robots and is capable of producing them also. But let's not spoil the surprise.

REST demands that a RESTful API is navigatable. This means that basically you only know one URL and that's the entry to the API. Ever other URL is under the control of the server and will be provided. So no URL building by the client. See Roy Fielding's comment on this: REST APIs must be hypertext-driven

An API based on CRUD operations (create, read, update, delete ) provide a interface to data. Most of the time they are an interface to a database over HTTP. This is fine for several use cases.

This tutorial will aim for a different kind of API where we access the domain logic through REST. This enables us to use the API with different clients without duplicating domain logic code.

I will use the Siren hypermedia format. It supports Actions which are very useful to access available domain operations. Also Siren is quite clear and straight forward.

It is very useful to have a fixed format for error reporting so clients will know what objects to expect if something goes wrong. See RFC7807 - Problem Details for HTTP APIs

The server application will be build following principles of Clean Architecture and Domain Driven Design. Both are very useful ideas and worth a lot of reading on their own.

Great reads:

• The Clean Code Blog by Robert C. Martin
• Clean Architecture: Standing on the shoulders of giants
• DDD, Hexagonal, Onion, Clean, CQRS, … How I put it all together

• C# ASP.NET Core for the server implementation.
• Web API Hypermedia Extensions I am the maintainer of this project and it will do a lot of work for me. Basically it is a Siren formatter which also builds links so I don't have to.
• Postman: super useful tool to talk to a HTTP API
• HypermediaUi I am also the maintainer of this project. It is a generic Siren browser and convenient during development.
• HTTP as the underling protocol, REST does not exclude other protocols at all.

During the tutorial we will build a ASP.NET Core application called RoboPlant. You can find the sources here: RoboPlant

• Part 0: Setup
• Part 1: Enter the RoboPlant
• Part 2: Linking to another resource
• Part 3: Communicating Errors