Deciding how to design a digital architecture that provides optimum agility and scale-ability for your organisation is a challenge for many architects in the midst of a digital transformation. Deciding if you should use APIs in your integration layer is perhaps much less of a dilemma (hint: of course you must). But then working out how to design those APIs and the services behind them can be a new problem to solve.
I think this is an especially important decision, as it is quite hard to undo an architectural choice. Issues, can subsequently occur such as:
All of which could have major implications in the future.
- performance bottlenecks (e.g. from too course a design)
- too much 'chatter' (e.g. from too granular a design)
- the inclusion of too much (any?) business logic
All of which could have major implications in the future.
No comments:
Post a Comment