A Digital Transformation story: Enterprise Integration through DevOps driven iPaaS API architecture

A reference architecture of the Integration factory: An iPaaS integration through a DevOps driven iterative APIfication. Before moving forward, let's do a quick recapitulation of where we had left from in the part 1 of this post. The following figure denotes the idea what we were toying with - i.e an API or Integration factory iterating through the cycles from ideation, design, construction and optimize.  Figure 1: An phased and iterative iPaaS re-platforming model Let's now focus on the DevOps architecture of the iPaaS which will deliver this integration. As we see that the cycle runs through an ideation->creation->optimize->ideation approach. The DevOps is delivered through a continuous integration / deployment / development pipeline which is built on Jenkins. The infrastructure are also provisioned using Vagrant as well as cloud tools - depending on which stage of the pipeline it is being provisioned. The architecture is a high level one -...

The problem domain: A typical enterprise technology landscape The enterprise IT landscape of a corporate house typically consists of a conglomerate of disparate technology stacks - ranging from huge legacy proprietary monoliths hosting the systems of records to the modern componentized systems of engagements. The very diverse nature of the 360 degree landscape involves diverse skills, reciprocal governance needs and completely different program governance strategies. The problem at hand is how to integrate such a complex landscape.  Figure 1: An interconnected but disparate enterprise technology landscape The solution: A hybrid integration powered Digital transformation in multi-speed IT We have a challenge here somewhat similar to an object constrained to move in a specific track and direction only, but being driven by internal tools that essentially are multi-sized and multi-speeds. The solution ask can be visualised as the combination of different s...