The Need For REST Certification
The other day I heard Morgan Freeman and some acting colleagues read the United States Declaration of Independence aloud. Each word in the Declaration was carefully selected for meaning, brevity, and exactness. Is it possible to have such clarity in technology?
REST is the wild, wild west of architecture. People in the industry create a URL pointer to a SOAP backend and call the URL pointer a REST API.
Similar to how SSLs are issued through organizations such as Verisign and Thawte, there should be an authority that issues certifications for REST URIs.
Generally, I find the use of the acronym REST next to the acronym API a mistake. REST and API. Think about these two acronyms next to each other. Really, give the juxtaposition some thought.
If your brain doesn’t explode from trying to reconcile the two acronyms then let me try to help you, so your brain does explode.
Often REST is used as an adjective to describe an API, which is not correct. Using the concept REST API literally means an architectural style that transfers a web resource’s state application programming interface, how can the meaning make sense?
Boom!! That should be your head exploding.
Pointing a URL to SOAP, a server class or method does not automatically create a REST resource. REST is a stateless, exploitation of Internet language and protocol for accessing characteristics or attribute/s (data) using the predefined HTTP action words GET, PUT, POST, and DELETE.
Many APIs defile the stateless constraint, which I could list as a separate article.
Consequently, there is no better time for someone to create a REST certification process than now. A certification process would ensure the resource is adhering to all the proper REST constraints, and ensure the resource is safe for use.