DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • The Five Stages of AI Adoption: A Practical Maturity Model for Software Teams
  • Bridging Gaps in SOC Maturity Using Detection Engineering and Automation
  • AI Maturity Is the New Differentiator: Why Operationalization Matters More Than Model Capability
  • Have Maturity Models Become Irrelevant?

Trending

  • A Walk-Through of the DZone Article Editor
  • Microsoft Fabric Throttling: Diagnose Before You Scale
  • Evaluating RAG in Production — What the Numbers Actually Revealed
  • Why Your Test Automation Is Always Behind the Code And the Architecture That Fixes It

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

What Is the Richardson Maturity Model (RMM)?

In this article, we take a look at the four types of REST APIs delineated by the Richardson Maturity Model, and what each of them means for your APIs.

By 
Andre Luis de Oliveira Dias
·
Jan. 11, 18 · Analysis
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
14.6K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

The Richardson Maturity Model (RMM) is a model developed by Leonard Richardson that helps organize your REST APIs into four levels, described below.

The main reason for this model to exist is to foster the evolution of the REST APIs of some system with a constant concern for governance, sense of organization with retro-compatibility, and constant improvements, using all the characteristics available from the REST architecture style.

Levels of RMM

Level 0 ( Swamp of Pox) - you should have a service already exposing a resource via its URI using only one HTTP verb (usually GET or POST). In this phase, you only use HTTP as a transport system (think of it as an RPC using HTTP).

Level 1 (Resources) - in this level you talk directly with your resources, correctly defined, using the appropriate division for it. Examples:

  • Resource 'hotel':
  • Resource 'room' (from Hotel):
    • services/hotel/1/rooms/all (or services/hotel/1/rooms) = should bring details of all rooms of the hotel with ID #1.
    • services/hotel/1/room/1 = should bring details of the hotel room with ID #1 from hotel #01.
  • Here the details of a hotel could be its location, how many stars it has, how many rooms, etc.
  • Here details of the room could be the installation details, size, if it's occupied, etc. 

Level 2 (HTTP Verbs) - you have a clear understanding of the semantics of HTTP verbs and can now map your service operations using HTTP verbs accordingly, using GET, POST, DELETE, PUT (most common verbs used in this Level), standardizing your access to your service's resources.

Level 3 (Multimedia) - you now can extract the maximum benefit from the HTTP protocol and services resources using Multimedia (HATEOAS). This level the API should help with the discoverability of all resources associated with the payload requested, via links available within the payload itself.

This model is heavily used with Microservices Architecture Style once you need to expose your services via on a standardized, easy-to-maintain, and organized API.

Make microservices happen in your company. Start today!

Thank you very much for the reading.

For more information, please check: Richardson Maturity Model

Maturity (geology)

Published at DZone with permission of Andre Luis de Oliveira Dias. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • The Five Stages of AI Adoption: A Practical Maturity Model for Software Teams
  • Bridging Gaps in SOC Maturity Using Detection Engineering and Automation
  • AI Maturity Is the New Differentiator: Why Operationalization Matters More Than Model Capability
  • Have Maturity Models Become Irrelevant?

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook