Requiring at least one product and one engineering, as well as other potential stakeholders involved through the API lifecycle from define to production, ensuring there is always someone actively owning and leading APIs forward.
Teams
Rules
APIs.json Apis Properties Teams Info
This property ensures that there is a reference to the team behind an API, providing a reference to business and engineering stakeholders
Strategies
API Development Is Collaborative Across Teams
API development must be a collaborative effort across product, engineering, and operations teams, with shared workspaces, design reviews, and cross-functional feedback loops that ensure APIs reflec...
APIs Always Have Well-Defined Owners and Stakeholders
Each API should ideally have a dedicated product as well as an engineering owner, with other stakeholders across the API lifecycle defined in an easy to access human readable location, but also def...
Lifecycle
dns Domains Define
Every API begins with the domain it serves. Before I write a single line of a definition I get clear on the business domain, the bounded context, and who owns it, because the domain is what keeps a...
