API maturity
When designing APIs, we adhere to a certain set of rules. Usually, these rules would be the design constraints specific to the architectural style we have chosen. In our case, that would be REST. Additionally, we aim to follow a set of guidelines, such as industry best practices or internal organization rules. This is a crucial step to ensure our API’s quality as early as possible in the design stage of its life cycle.
In this section, we examine two models for assessing API design maturity. Maturity models provide a structured way to validate and score the quality of an API design. We begin with the Richardson Maturity Model (RMM), which evaluates how closely an API aligns with the constraints of the REST architectural style. Next, we turn to the Web API Design Maturity Model (WADMM), which focuses on assessing how client-centric an API is through the design of its document model. Let’s explore each of these maturity models in more detail.
