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 …
Obviously, data cannot move itself. A processor somewhere must pick up and move data somewhere else. So, while in the previous blog article of our series Data Integration Best Practices we talked about HOW we can move data, this time we are going to see WHAT moves data between systems and the design choices that we need to consider for …
Moving on to the next chapter of our blog series, namely about different types of integration, in this article we’re going to explore the main two types of integrations: asynchronous integration and synchronous integration. Whether you need a fast response of the systems involved or the results to be delivered further in the future; both, request-replay or asynchronous integration, offer …
As we mentioned at the very beginning of our blog series, all integration problems essentially fall into two large categories: the problems that have to do with the technical mechanics of integration and the problems that concern the correct application of business rules. There are, however, certain types of problems that originate in both. In this article, which is closing …
So far, we have addressed only the problems that concern the pure technical mechanics of integration. Now it’s time to review the challenges that are related to the correct application of business rules. These are, as we stated in the first article of our blog series, typically of higher level in nature and answer the question of “What?”. And the …
Let us first make it clear what ID linking is about and what it has to do with data duplication. To do that, let’s take CRM systems as an example. It is likely there are more than one person in a system who share the same first and last names. And it is inevitable that sometimes, some pieces of information …
In order for the data exchange to happen, there must be a way to connect to a system in the first place. Here, there is a difference between on-premises and cloud-based systems.
