Know how RESTful your API is: An Overview of the Richardson Maturity Model – RHD Blog
Let’s say we designed a REST API. How do we know how much Restful API is? Some developers call it “Not Restful API”, some call it “Partially Restful API”, for some, it is “Fully Restful API”, and for some “It is not REST API at all or they call it SOAP based web service”. Imagine it as a spectrum from Not Restful to Fully Restful API.


  1. Tomi Engdahl says:

    Get started with REST services with Apache Camel

    REST services can be used for data access APIs, sending information from devices to the cloud, monitoring, and more.

  2. Tomi Engdahl says:

    Securing a REST Service

    If you’re building a REST service, then that REST service will expose some kind of data or will allow some kind of interactions with a server.

    How to Secure a REST Service
    For Java EE Security/the Payara Platform, there are a couple of options:

    REST Services can be secured by defining constraints on the URL, endpoint (resource class), or method level.
    An authentication mechanism can be chosen from those defined by the Servlet API, by the Java EE Security API, or a custom (application provided) one can be used.
    An identity store can be left undefined by the application and left to be configured within Payara Server (for example, using the admin console or CLI), one can be chosen from those defined by the Java EE Security API, or a custom (application provided) one can be used.

  3. 5 letter words says:

    We are indebted to you for making these resources accessible to us. There are a number of articles that I have read that are on similar topics, but none of them go into as much detail as this one did. I have the intention of expanding both my education and my experience.


Leave a Comment

Your email address will not be published. Required fields are marked *