All APIs should be high quality and reliable, providing adequate levels of monitoring of its availability and performance, with the proper provenance and communication with producer and consumers regarding quality of the APIs, as well as with any future release of API resources.
APIs Are Always High Quality and Reliable
Policies
Status
Status pages and monitoring reports are how you maintain trust with consumers. Showing current and historical uptime transparently is way more effective than pretending everything is always fine.
Performance
Performance data complements status and uptime by drilling into the details that matter -- speed, latency, and throughput. Publishing this openly is how you show consumers you take reliability seri...
Experiences
Automation
I keep shining a light on automation because it's the only way to scale API operations. When testing, validation, deployment, and governance are all manual, you're just adding human error and slowi...
Communication
I struggle with how little communication happens between the teams producing APIs and the people consuming them. Blogs, changelogs, roadmaps -- these are building blocks that most teams just skip, ...
Quality
I see the quality of APIs eroding across the landscape. Teams ship fast and never look back, but consumers feel every rough edge, every missing example, every inconsistent response. Quality is what...
Reliability
Reliability is where the rubber meets the road in the API landscape. If your APIs aren't up when consumers need them, and if new versions don't land smoothly, none of the other building blocks matter.