The 3 REST API Maturity Levels (The Richardson Maturity Model)

Join us on Discord, get the source code (and support the channel 🙂): / amantinband
Clean Architecture Zero to Hero: dometrain.com/bundle/from-zer...
Domain-Driven Design Zero to Hero: dometrain.com/bundle/from-zer...
All videos in this playlist: • ASP.NET 8 REST API Tut...
Act Three: The Maturity Heuristic: www.crummy.com/writing/speaki...
In today's video we'll talk about the Richardson Maturity Model (the 3 maturity levels as defined by Leonard Richardson in 2008)
Level 0: Single Endpoint, Single HTTP Method
Level 1: Multiple Endpoints, Single HTTP Method
Level 2: Multiple Endpoints, Multiple HTTP Methods
Level 3: Multiple Endpoints, Multiple HTTP Methods + HATEOAS
Connect with me on 'em socials:
Twitter: / amantinband
LinkedIn: / amantinband
GitHub: github.com/amantinband
Check out all my courses on DomeTrain:
dometrain.com/author/amichai-...
Support the channel and get the source code:
/ amantinband
Thanks for watching, don't forget to like & comment & subscribe! ❤️ 💻

[@tchial0]

I like the way you come up with theories and origins before you get your hands dirty with code.

[@deeplerg7913]

Nice! No bs, straight to the point. Not trying to artificially prolong the video with long-winded explanations. Just how it should be.

[@devmarkmonster]

I only did level 3 once, it was a lot of work to make it work nicely according to the standards. In the end we noticed that the supplier that created the ios and android apps more or less ignored the links that we so carefully put in the response, when we thought of changing an endpoint that wouldn’t break because our users would get it out of the links section we had to rollback the release. So sticking with level 2 for now until a requirement for 3 shows up.

[@alexboc74]

Very nice video! Just a question out of scope, which software are you using to draw on the screen ? Its really cool!

[@tchial0]

A video of creating a level 3 API from scratch would be

[@moritzvogel6450]

We actually use Hypermedia in our company, and it really has some nice benefits that you just get as an effect :) Change the key of an entity? No problem, no changes in the client required

[@SpaceShot]

I'm curious what your thoughts are on apis where the parameters are to be kept confidential. In other words, while from a technical perspective one could create uris that represented the resources meeting a level 2 maturity model, it is desired to keep those parameters hidden. Second, it doesn't seem wise to use GET with request bodies to gain TLS support for that encrypting that data. Otherwise, remaining principles are all fine. Do we simply say well, we can't use this and move on, or am i being short sighted about something? Don't get me wrong, I am all for using the terms correctly and it has never bothered me to say I'm building a Web API to contrast it from REST. Just wondering if i need to rethink the scenario because I'm missing something.

[@ansgarhellwig6700]

Query parameters are already encrypted when using TLS (HTTPS), what do you mean by "hiding" those parameters?

[@netssrmrz]

Good video. Regarding the subject, the term "maturity level" sounds conceited to me. How many of the other protocols not running on port 80 and 443 do you think use HTTP methods? I'm guessing none. And If there was a dedicated port for browser APIs I'd bet it wouldn't be based on HTTP or REST.