Use a general purpose language to manage the interface evolution

Many commercial integration tools market their ability to own the integration landscape and call out to general purpose languages as needed. While I can appreciate the marketing behind such messaging — it promotes product penetration and lock-in — as architectural guidance, it is exactly backwards. Instead, we should almost always manage the interface evolution in a general purpose language for at least two reasons: so we can better manage the complexity of maintaining a clean interface, and so that we avoid the gravitational pull of our tool's mental model when making strategic integration decisions.

more… https://martinfowler.com/articles/cant-buy-integration.html#UseAGeneralPurposeLanguageToManageTheInterfaceEvolution

Creato 3y | 7 dic 2021, 15:20:20


Accedi per aggiungere un commento

Altri post in questo gruppo

How is GenAI different from other code generators?

How is code generation with GenAI different from more "traditional" code generators? The newest memo in Birgitta Böckeler's explorations of GenAI talks abou

18 ott 2023, 20:10:05 | Martin Fowler
How is GenAI different from other code generators?

How is code generation with GenAI different from more "traditional" code generators? The newest memo in Birgitta Böckeler's explorations of GenAI talks abou

19 set 2023, 10:10:06 | Martin Fowler
TDD with GitHub Copilot

At Thoughtworks, we are strong practitioners of Test Driven Development (TDD). Naturally this leads to the question of how generative AI can

17 ago 2023, 20:30:07 | Martin Fowler