Today, you will learn the concept of Richardson’s Maturity Model(RMM), the key concept behind REST APIs.<\/p>\n
So, how do you measure if a web service is REST web service or not?<\/p>\n
This can be done using a model developed by a Computer Scientist called Roy Fielding. This model is called Richardson’s Maturity Model <\/i>and is use to determine how much the API conforms the certain architectural styles.<\/p>\n
It is used to answer the question: How RESTful is the API?<\/strong><\/em> Based on certain criteria, a REST API can can score from 0 – 3 ranging from Not-RESTful (level 0) to Fully-RESTful(level 3)<\/p>\n <\/p>\n Content<\/b> <\/p>\n At level 0 a REST API is described as not RESTful. This means that the API is made up just XML and therefore known as ‘Swamp of POX’, plain old xml. At level 0, the request and response uses just on entry point URI and just one method HTTP POST method. Level 0 is equivalent to SOAP(Simple Object Access Protocol) web service<\/p>\n <\/p>\n Level 1 has to do with Resource and Resource-based URIs. This means that there are different URIs for different resources in the API. URI stands for Universal Resource Identifier. It is similar to a URL. The difference is that a URI is a URL that maps to a particular resource. Take example of URL from a messaging application:<\/p>\n http:\/\/kindsonthegenius.com\/messages<\/span><\/span> <\/p>\n So if your REST API has the URIs designed this way, then that API have attained to REST level 1.<\/p>\n <\/p>\n If a REST API implements resource-based URIs and also uses the appropriate HTTP verb to perform operations, then the API have attained REST level 2. So if a client makes a request to retrieve a resource from the server, the it should use the REST the GET method. <\/ins> To attain level 3 after attaining level 2, then the API must be HATEOAS compliant. HATEOAS stands for Hypermedia as the Engine Of Application State. Of course you know what Hypermedia is. Typical example is hyperlinks. So this level requires that the API must provide in addition to the response, links to other resources or operations that the client may need. This level is what makes is possible to browse a website without much help because the hyperlinks and images provide the user with hints on how to move to a different part of the application(changing the application state)<\/p>\n <\/p>\n So a REST API at level 3 is described as fully RESTful. I hope this explanation is clear. Please leave a comment if you would like to.<\/p>\n","protected":false},"excerpt":{"rendered":" Today, you will learn the concept of Richardson’s Maturity Model(RMM), the key concept behind REST APIs. So, how do you measure if a web service … <\/p>\n","protected":false},"author":2,"featured_media":776,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_mi_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0},"categories":[289],"tags":[],"_links":{"self":[{"href":"https:\/\/kindsonthegenius.com\/blog\/wp-json\/wp\/v2\/posts\/229"}],"collection":[{"href":"https:\/\/kindsonthegenius.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kindsonthegenius.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kindsonthegenius.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/kindsonthegenius.com\/blog\/wp-json\/wp\/v2\/comments?post=229"}],"version-history":[{"count":9,"href":"https:\/\/kindsonthegenius.com\/blog\/wp-json\/wp\/v2\/posts\/229\/revisions"}],"predecessor-version":[{"id":1261,"href":"https:\/\/kindsonthegenius.com\/blog\/wp-json\/wp\/v2\/posts\/229\/revisions\/1261"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/kindsonthegenius.com\/blog\/wp-json\/wp\/v2\/media\/776"}],"wp:attachment":[{"href":"https:\/\/kindsonthegenius.com\/blog\/wp-json\/wp\/v2\/media?parent=229"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kindsonthegenius.com\/blog\/wp-json\/wp\/v2\/categories?post=229"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kindsonthegenius.com\/blog\/wp-json\/wp\/v2\/tags?post=229"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nLevel 0: Non RESTful<\/a>
\nLevel 1: Resource-based URIs<\/a>
\nLevel 2: Use of HTTP Methods<\/a>
\nLevel 3: HATEAOS-Compliance<\/a>
\nFinal Notes.<\/a><\/p>\nLevel 0: Not RESTful<\/strong><\/h4>\n
\nLevel 1: Resource-based URIs<\/strong><\/h4>\n
\n
\nResources are endpoints in the API which could represent an object, collections of objects, operations on objects etc.<\/p>\n
\nhttp:\/\/kindsonthegenius.com\/messages\/1<\/span><\/span>
\nhttp:\/\/kindsonthegenius.com\/messages\/2\/delete<\/span><\/span><\/p>\n\n
Level 2: HTTP Methods (or Verbs)<\/strong><\/h4>\n
\n
\nThe HTTP verbs corresponds to the four CRUD operations that can be performed on a resource. The verbs are:<\/p>\n\n
\nThe fact is that without the use of HTTP verbs, the API would still work but would not be fully RESTful.<\/p>\n
\n<\/b><\/p>\nLevel 3: HATEOAS Compliant<\/strong><\/h4>\n
\n
\nSo if a client request for a resource, say a user profile, then the API should provide the user with links to Edit, Delete and Save as well as link to get list of users.<\/p>\nFinal Notes<\/strong><\/h4>\n
\n