Application integration is essential for any successful digital transformation initiative. From Gartner:
“Application integration is the process of enabling independently designed applications to work together.”
Tips, Expertise, Articles and Advice from the Pro's for Your Website or Blog to Succeed
Application integration is essential for any successful digital transformation initiative. From Gartner:
“Application integration is the process of enabling independently designed applications to work together.”
I recently took a look into the DZone Integration Zone, and it was globally all about APIs. How to design APIs, test them, use the latest framework, and so on. But it would be a bad idea to forget that there are many things to integrate!
You might also like: Introduction to Integration Patterns
Change data capture, or CDC, is a kind of technology that synchronizes two data sources together. The synchronization can be bi-directional, and everything's made to make it very simple. Just choose the tables you need to synchronize, and if needed, it will also create new tables in the target database. Of course, you can define other existing tables in a simple manner, it’s up to you!
While understanding the importance of the APIF, we also recognize that good architectural practices and proper logical architecture of the application/services could be even more important than the service mesh. To support the integration strategy, CIBC has been developed Integration Pattern, which makes internal and external APIs the emerging standard for integration across the bank and beyond. This pattern transitions from existing legacy integration components and patterns to modern equivalents that embrace APIs and (micro)services by truly distributing all gateway and isolation layer functions.
The CIBC Integration Pattern is presented in the following diagram:
With emerging new devices and technologies in the last years, CIBC, as the entire industry, goes through enormous changes in all aspects of developing new capabilities and delivering business value. To address the new requirements CIBC embraced and promotes API Strategy which in turn requires new Integration Strategy. CIBC developed a generalized Integration Pattern to reflect these changes and related standards to enforce the pattern. The pattern is directly supported by the API Foundation Platform built in our organization. Successful implementation of the pattern requires a steep learning curve and critical thinking to navigate through zillions of buzzwords to understand what would be the best possible solution for a concrete use-case.
The article discusses major decisions architects and designers should make to apply the pattern: what API protocol to choose? What would be the right architectural style to implement the API? What is the recommended roadmap, and the best strategy to progress from one architectural style to another one, say from a legacy application to a structured monolith, and then, if required to microservices? What are the options to implement the isolation layer? What design patterns to use to implement Cross-cutting concerns (XCC)? And what about eventual consistency?