Due to the Digital Transformation programs that companies embark on we see that integrations are becoming an increasingly important part of IT budgets. According to Gartner, 50% of all IT budgets in 2020 will be spent on the right way to integrate systems and processes. The trend of using best of breed solutions through the emergence of low code application development means that it’s becoming easier to solve specific processes within an organization through the development of single applications.
This development results in an increasingly fragmented IT landscape, which ultimately leads to severe integration issues: what information has to be available where and when? Which data is leading? Do the applications speak the same “development language”?
Point to point connections
With point to point connections, applications are directly linked on a one on one basis. Data is exchanged between these applications. Logically, the amount of point to point connections with multiple applications in your landscape will increase exponentially.
See the graph below.
Whereas with 3 systems the number of point to point connections is still three, with 10 systems this numer has already increased to 45 connections. A recipe for spaghetti!
Not every application needs to be integrated with every single other application, but the graph clearly shows the impact of adding a 12th application.
The negative impact on time, money and quality by adding or replacing applications in the point to point scenario is nearly disastrous. Next to that, risk of mistakes and instable network traffic are high.
Structure your complexity; scale expansion of applications with a CDM
So how do you scale up your integrations landscape in a proper way? By using the CDM. The
CDM is often referred to as the common data model: one language that connects all applications. Thus enforcing standardization of data defintions. This CDM wil hold the single integration model for your company – one truth.
Key advantages of a CDM
- Easy overview: All integrations are implemeted in a single model. There is one location where you can see all involved systems and integrations.
- One single language: All applications are translated back to a single model: the CDM. Interpretation of data is managed on a central level.
- Scalable: Adding or replacing applications means translation tot the CDM, not to all other applications and systems. The CDM will manage this automatically on a central level.
- Speed of development: Connecting applications to the CDM is a single operation. Connecting aplications point to point are multiple operations, which results in more effort and duration.
Key considerations when setting up a CDM
There are a few considerations to take into account when designing your CDM:
- Initial investment: The setup of a CDM will take more time and effort at start-up time. But after three applications, it is becoming more easy and the relative time and effort per integration will drop dramatically.
- Implementing and maintaining a CDM is not a rush job – doing the job first time right results in direct benefits.
- Considering future evolutions in your integration landscape so you can already take that into account when designing your futureproof CDM.
- A CDM remains custom for every organisation despite the fact that there are many standard connectors for applications and systems.
Simplify replacing Legacy systems!
When replacing legacy systems or adding new systems or applications, you only have to connect these to the central CDM. If you continue to focus on the goal to have a scalable integration landscape, you will find out that the CDM provides that overview and scalability
In my next blog, I will eleborate further on the key elements to translate vision to a working integration model. The focus will be on different integration patterns possible which helps in this ongoing endeavour.
Thanks for reading this article. Do you have questions or want to know more? Please fill in the form below. We will contact you soon.
If you are interested in more knowledge, please read this article about microservice architecture.