Data integration platforms: the main pros and cons explained

When choosing a data integration platform, do you build everything yourself or rely on standard building blocks? And from what size does such a platform become beneficial? Although there are arguments for both approaches, most organizations eventually choose standardization. Below are the three main advantages and disadvantages of using a data integration platform.

Building blocks for grown-ups. It may sound unusual, but it is very much the future of enterprise IT. More and more organizations recognize the benefits of a data integration platform built on standardized components. At the same time, an organization needs to have a certain scale in order to realize the full benefits. As a rule of thumb, the lower limit is roughly one thousand employees.

Learning through trial and error

Data integration platforms are not new, which means many organizations have already worked with them. Some have learned the hard way and now understand the advantages and disadvantages from experience. So what are the real pros and cons?

Here are the main advantages of a data integration platform that uses standard building blocks:

  • Functional and technical components are separated. A technical specialist builds the technical layer, while a business expert takes care of the functional logic. The two are connected using methods such as low code.
  • All integrations are built in the same way. This creates consistency and makes developers or application administrators more interchangeable. The more integrations you create, the greater the benefits. Application management becomes more uniform as well.
  • Reliable message delivery. You exchange messages between systems, but what happens when one system is temporarily unavailable? A standard data integration platform ensures that messages can always be resent in the same way across all integrations.
  • Lifecycle management and security are taken care of. When you choose a standard framework, the vendor maintains the underlying code and security updates. As a user, you benefit from continuous improvements and proven security.

There are disadvantages as well, although only a few:

  • You need functional specialists to build integrations. This introduces a layer of overhead, since these roles are necessary to configure and manage integrations.
  • Initial integrations may take longer to build. The first set of integrations often requires more work than a custom-built solution. However, once the foundation is in place, the pace accelerates. The same applies to ongoing maintenance.
  • The scope of the platform limits full freedom. Working without an integration platform gives you complete flexibility. A standard solution limits that to some degree, because you operate within the boundaries of the platform.
  • Not every platform is suited for high performance use. If you need high throughput, you must evaluate the options carefully, because not all standardized integration platforms meet these requirements.

Data integration platforms: avoiding the knowledge drain

There is one more important argument for choosing a standard data integration platform. Any developer can create an integration between two systems. As long as that developer stays employed, changes and incident resolution are no problem. But what happens when that developer leaves the organization? With a standard platform in place, people are far more interchangeable. The required technical skill level for maintenance can also be lower.

A Dutch platform means shorter lines and more influence

There is another factor. Most integration platforms are created by large international vendors, not by Dutch IT companies. The Frank!Framework, a data integration platform originally developed by WeAreFrank!, is an exception. This brings two clear advantages. Communication is always in Dutch, and if you request a new feature or improvement, the turnaround time is much faster than with major international suppliers. The platform offers uniformity, separates technology from functionality, is easy to manage and monitor, requires fewer highly technical staff, and provides strong security. It also enables direct communication between WeAreFrank! and users of the platform. In our view, that is a clear win-win.

Questions about this case?
Get in touch
Portrait of Erwin Beets

Written by
Erwin Beets

Need advice on IT architecture? Request a consultation