Modern Integration Architecture with LeanIX

Learn more about Integration Architecture: www.leanix.net/en/integration...
If you want to listen to more presentations of EA Connect Days 2020, check out the other live recordings: www.eaconnectdays.com/eu/2020/
Two representatives from Deloitte Consulting - Philipp Wagner (Manager, Technology Strategy & Transformation) and Gabor Vincze (Manager, Technology Strategy & Architecture) - took to the stage to share a case study on Modern Integration Architecture with LeanIX. The client in this consultation sought to establish a modern integration architecture capable of generating:
• Opportunities for different consumers to access client source data
• Holistic API management with a common governance structure
• A data virtualization layer for interconnectivity across different domains and systems
• A set of future proven technologies
• A trusted platform that controls the access and approval workflow to data across all departments or regions
And Deloitte’s solutions for doing so were based on three central hypotheses:
(1) that SAP technologies could integrate the client use cases, long-term, and with the future proven technologies wanted; (2) MuleSoft could represent a long-term solution to cover all requirements for integrations; and (3) MuleSoft could also be combined with SAP technologies to cover the client use cases, long-term, with future proven technologies.
To prove this, Deloitte used LeanIX to model combinations of the above scenarios so the client could gain a clear understanding of how it might best reach the target modern Enterprise Integration Architecture. The benefits and shortcomings of displaying this information via LeanIX were summarized by Vincze and Wagner as follows:
• By modeling the API integration as an IT component, they were able to create a direct link to the applications connected to the middleware without needed to “double-model”. One of the drawbacks of doing so, however, was that there was no way of showing connections between individual middleware instances.
• By modeling API integration as an application, they could provide visibility across most LeanIX reports given that the reports themselves are application-centric. Doing so unfortunately meant double-modeling middleware application as an IT component in order to enable a technology matrix and landscape report.
• By modeling the integration architecture with a point-to-interface (an approach that’s essential for legacy interfaces), they benefitted from a clearer way of defining the ownership of applications and being able to add manual interfaces relevant from a business standpoint.

[@manjerekarrao]

How to automate the integration of creating factsheet from a custom application?