mirror of
https://github.com/adidas/api-guidelines.git
synced 2025-10-25 15:19:19 +00:00
API first
API first
This commit is contained in:
@@ -1,11 +1,12 @@
|
||||
# API First
|
||||
|
||||
1. Development of an API MUST always start with API design.
|
||||
1. API design SHOULD be realized following the **API design process**
|
||||
1. API design SHOULD be realized following the **API design process**.
|
||||
1. An API design MUST be formalized in a form of an API description using **Swagger** and stored in [Apiary](./apiary.md).
|
||||
1. **API description is master of truth, not the API implementation.**
|
||||
|
||||
> FURTHER NOTES: API first approach is crucial when adopting the Microservice architecture.
|
||||
> NOTE: API first approach is crucial when adopting the Microservice architecture.
|
||||
Describing what API is supposed to do also helps all stakeholders to align and better understand what will be delivered at the end.
|
||||
It's not acceptable that API is developed first and later on described in some proprietary format.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user