Mirrors/api-guidelines
1
0
Fork 0
mirror of https://github.com/adidas/api-guidelines.git synced 2025-10-25 15:19:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updates core-principles/api-first.md

Browse Source 
Auto commit by GitBook Editor
This commit is contained in:
oonovak
2017-02-13 16:20:31 +00:00
parent 1a91434071
commit 3190a14005
1 changed files with 2 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
core-principles/api-first.md
View File

@@ -4,7 +4,7 @@ Everyone **MUST** follow the **API first** principle.
**API first** principle is extension of **Contract first** architecture principle.
Therefore development of an API **MUST** always start with **API design** without any upfront coding activities.
An API design **MUST** be formalized in a form of an **API description** using [Open API Specification](./openapi-specification.md) and stored in adidas [API design platform](./apiary.md).
An API design **MUST** be formalized in a form of an **API description** using [Open API Specification](./openapi-specification.md) and stored in adidas [API design platform](./apiary.md) and agreed by all stakeholders.
> NOTE: It's not acceptable that API is developed first and later on described in some proprietary format.
@@ -12,8 +12,7 @@ Clearly describing what API is supposed to do before coding it, helps to facilit
It also helps to establish governance on API's to check that certain quality is met and API guidelines are being followed.
**API description is master of truth, not the API implementation.**
It's MUST to adhere to the statement above as this is basis for adoption of Microservice architecture pattern. It's absolute MUST that implementation never brea
API implementation **MUST** always be compliant to respective API description which represent the [Contract](./contract.md) between API and it's consumer.