Skip to content

Commit ace10f5

Browse files
committed
api led 2 link p1
1 parent fd6a766 commit ace10f5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/en/blog/the-problem-with-api-led-part-2.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ tags: [ "integration", "api", "patterns" ]
77
categories: [ "integration" ]
88
---
99

10-
In the first part of this series, I talked about the issues around the name "API-Led." For some time, I thought we could address this problem by clarifying further what API-Led is and isn't and proposing a different name. In fact, during our time at MS3, my friend Josh Erney (the DataWeave guru) and I collaborated to clarify what an API-Led implementation should look like. Alas, the article never came to light.
10+
In the [first part](https://josemontoya.io/blog/the-problem-with-api-led-part-1/) of this series, I talked about the issues around the name "API-Led." For some time, I thought we could address this problem by clarifying further what API-Led is and isn't and proposing a different name. In fact, during our time at MS3, my friend Josh Erney (the DataWeave guru) and I collaborated to clarify what an API-Led implementation should look like. Alas, the article never came to light.
1111

1212
However, after years of seeing organizations struggle to implement it correctly and experience some pain even when they get it right, I realized the pattern does not fit modern organizations, even without misuse. Though it may be possible to address some of its issues, I'm not convinced it's worth the necessary effort. We should move on from it entirely.
1313

0 commit comments

Comments
 (0)