AJR/TechradarDev
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: fix spelling issues in v5 release (#165)

Browse Source
This commit is contained in:
Stefan Rotsch
2023-02-22 19:02:16 +01:00
committed by Bastian
parent 03783eee3b
commit 46c32eefbe
7 changed files with 74 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
radar/2022-03-28/api-first-design-approach.md
View File

@@ -2,10 +2,16 @@
title: "API-First Design Approach"
ring: adopt
quadrant: methods-and-patterns
tags: [architecture]
tags: [architecture]
---
The API of any software we develop shapes in which way developers, teams, customers and users interact with our software.
No matter if a Frontend-API like GraphQL, a rpc-API like gRPC or an internal API published by a module in a larger project or shared library, messing the API up always creates headaches and is hard to correct.
If we stick to semantic versioning, it's actually pretty impossible to change a once-published API without breaking consumers.
By todays standards we priorize API design before actual development, to be clear on how our software interacts, and thus move this pattern to "adopt".
The API of any software we develop shapes in which way developers, teams, customers and users interact with our
software.
No matter if a Frontend-API like GraphQL, a rpc-API like gRPC or an internal API published by a module in a larger
project or shared library, messing the API up always creates headaches and is hard to correct.
If we stick to semantic versioning, it's actually pretty impossible to change a once-published API without breaking
consumers.
By today's standards we prioritize API design before actual development, to be clear on how our software interacts, and
thus move this pattern to "adopt".