A Digital Transformation story: Enterprise Integration through a DevOps driven iPaaS API architecture - Part 2
![Image](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi44DpVSbxWjJwCHCqiZ5AfXptlBr-jq_EyveJpAEBcMunQGKJV1_DQ4SFwRu3EBiMGMB9Hw5ks_5XIXfgGM44r7UG9PxLjRWdsUJ5OoNIH8px1kLqffcPGFZueEflpJcPMCWJogQLXI3E/s1600/Phased+Approach.jpg)
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 -...