Resource Usage and Traceability
Another part of REST Governance is consumption. Consumption comes into play when building, deploying, and maintaining resources based on existing REST resources. Consumption resource tracking is essential for multiple reasons:
- support internally defined and externally imposed business governance mandates
- simplify the process of ongoing impact analysis and change management as resources mature
- provide a quantitative ROI based on real usage statistics back to the enterprise
Let’s take a quick look at governance mandates. Business level governance affects IT departments. Consequently, governance mandates increase audits and traceability requirements applied to an IT department. However, expanded requirements cannot be met without some form of usage registration.
Remember, resources change over time as new requirements are identified. Development teams need to stay fully abreast about planned and implemented changes to resources they use. Further, teams need to participate in requirements feedback, and prepare for the eventual obsolescence of back-level resources as new versions are deployed.
Ultimately, enterprises are not in business to serve IT. An organization’s management expect a quantifiable ROI from any REST initiative. Without service usage direct traceability a quantifiable ROI based on service use and reuse is almost impossible to produce. Further, if usage registration is built-in resource discovery is quantifiable. Instead of guessing, ROI is as simple as running a periodic report.