When you need two or more applications and services to exchange data between them on a regular basis, REST integration (or REST API integration) is one method that slowly but steadily gains status of the new and preferred standard. But as with any other project where you need to connect apps and web services via API, integrating REST requires good …

There is plenty of information on the different types of APIs, common API architectures and protocols, and such. So, instead of providing just general information like any other source you can find out there, I decided to take a look at all these concepts specifically from the integration perspective: What exactly working with different types, architectures and protocols of APIs …

In any application integration, data migration and in general, any data management initiative, data mapping is one of the most critical steps. One could even argue that the integrations project success depends largely on correct mapping of source to target data. So, let’s review what the data mapping best practices are: the types, the common approaches as well as the …

The iPaaS market is clearly growing now at a faster pace than ever anticipated. This is not only due to the pandemic forcing companies to accelerate the digital transformation, but also in general due to the rise of SaaS. The replacement of older, server-bound software solutions with more modular, user-friendly and flexible SaaS solutions means customers need to connect these …

There is hardly an IT application nowadays that doesn’t provide an API, which specifies how this application should interact with the rest of the IT ecosystem. So, it’s no wonder that IT staff even at large enterprises increasingly make use of APIs when they need to integrate multiple systems with each other, commonly new SaaS applications with the existing IT …

Webhooks vs API, oh well. When there is a talk about what method to use in order to seamlessly sync datasets between applications, platforms and databases (in other words, to perform application integration), APIs are often named as today’s best-practices method for handling this. Unlike ETL-based integrations, which are not scalable, quite expensive and a bad fit for dynamic changes …

In the previous article of our last chapter of Data Integration Best Practices, we took a look at how to describe integrations in such a way that everybody – from developers to business users – understands the requirements correctly. We also discussed why you eventually might need some type of an integration layer to keep your integration projects under control.  …

So far, in our blog series Data Integration Best practices, we have covered the different types of high-level and low-level problems occurring in data integration projects. We have also addressed the different types of integration, the systems that move data and even the pricing aspect of such a project. Ten articles later, we arrived at best practices moving forward.  In …

While defining a data integration project we should consider what, when and how we want to integrate. Once we have done this, we can move on with the last step of the plan: the costs. The billion-dollar question… how deep should we dig into our pockets?   If we want to have a realistic idea of the cost of our integration …

In the current chapter of our blog series on data integration best practices, we have already talked about different communication types for data integration – synchronous vs. asynchronous. We have also talked about the main difference between the types of systems that move data – direct data synchronization vs. an integration layer. In this installment of the series, we would …