Coding a REST API has never felt right to me. I believe that REST APIs should be designed and configured, but not coded. To that end, I’ve conceived of an alternative approach to REST API implementation that is founded on the WRML conceptual framework’s architectural principles. These principles, summarized below, align with the REST API design methodology presented as this book’s rules.
REST APIs, while becoming ubiquitous, are far from uniformly designed. The RESTfulness of APIs continues to be debated by those that create and consume them. In the absence of standards, REST API designers are free to innovate and explore new concepts, which is a good thing. However, when REST API designs eventually converge on a set of common patterns that address each one of the cross-cutting concerns, developers will benefit from the uniformity.
If history is any indication, this uniformity will most likely be driven by a pragmatic and detailed standard for REST API design. This book’s rule-based expression of a REST API’s expected behavior is a good indication that a more detailed specification can eventually be written to standardize a common approach. Then, this standard can be leveraged to develop reusable frameworks and libraries for clients, servers, and network-based intermediaries.
For interoperability’s sake, a REST API design standard must be neutral with respect to programming languages and representation formats. ...