Integration starts with a simple idea – the concept of connected apps. This makes it possible to introduce other ideas, such as service bus, service composition, and service virtualization, each of which can be applied to the architecture of an enterprise to deliver benefits. An evaluation of the needs of your enterprise can determine which of these ideas should be applied, and how they should be applied, in your integration architecture. And balance that with the costs of the different potential solutions.
A good API/Integration architect will always probe into the information given, about both requirements and solutions, to reach a level of understanding that goes deeper than the buzzwords. For example, it is often said that “APIs deliver enterprise agility”. What does “agility” mean for your enterprise? Is it the ability to re-combine existing functions to meet changing customer requirements? Is it the ability to develop new functions rapidly? Is it the ability to scale operations to meet different levels of demand? Within the broad concept of an integrated enterprise, there are three very different ideas that can help you meet these different agility requirements: service composition, model-driven development, and service virtualization. You can build all of these ideas into your APIs, but they each require different – and potentially expensive – supporting infrastructure. You must choose your solution to fit the requirements.
Endeavor IT is fully equipped to advice clients on the best solution to fit their unique needs.