How system integration methods evolved

With the increased desire and demand for data flow and system integration the integration methods changed. It started with a point-to-point integration and over time evolved into iPaaS solutions. Each method still serves a purpose and all of them are still used today. There is no bad or good, each method is simply more suitable in specific situations. However, in the methods we discuss there seems to be an upwards motion in scalability, security and manageability.

Point-to-point integration

Point-to-point integration is the most pure and simple form of integration; data travels from one end point to the other end point. It uses a script to extract data from the application, transforms the data to the format of the receiving application and sends it through.
point to point

The desire for being able to do multiple integrations and still maintain a manageable solution drove development further to other integration methods.

Hub and spoke integration

Hub and spoke integration
The hub and spoke concept finds its origin in the logistics industry. In a search for efficiency they started working with central hubs and lines or spokes travelling out of those hubs. This concept is translated into an integration model.

The hub and spoke integration method enabled businesses to create more elaborate and complex integrations. However, each application needs a hand written connector which still requires quite a lot of time and effort from developers. Also scalability was a limiting factor for enterprise applications.

ESB enterprise service bus

The ESB concept is based around the centralised Bus. This Bus arranges the integrations into backend systems and translations of data models, including deep connectivity, routing, translations and making the data available as service interfaces for reuse by new applications.
How does ESB work

The ESB method enables business to make complex integrations and keeps those manageable. With the rise of the cloud and cloud applications, the ESB method was not always as flexible as the business required it to be.


iPaaS is an Integration Platform as a Service. iPaaS combines application and data integration. It is an online software tool that allows users to design and create integrations. It can interact with both cloud applications and on-premise applications.

The evolution of integration methods is still continuing today and will continue to do so in the future. It is constantly adapting to the evolving requirements.

Which system integration method does Dovetail use?

Dovetail is an iPaaS; integration Platform as a Service. However Dovetail has some additional features; it is a no code/low code solution, so no programmer is required to build your solution. In the graphic interface you can create your documentation whilst you build. Lastly, testing and putting flows live can be done in the same environment – putting you completely in control thanks to smart version management.

Want to know more about what Dovetail can do? Continue reading

Related resources

How to replace a library from 2010?

In Dovetail 4.15 we transitioned to Jackson to ...

If you don’t test restores, you don’t have backups

It is as simple as the title suggests: “If you ...

Automated processing of all sales order related flows

As a sales organisation, you aim for a streamli...

Challenges with entering data in multiple systems

What challenges or pain points do you face? And...