Let me start by thanking all those who read the first part of our blog series on converting legacy ETL to modern ETL! Before I begin the second part of this three-blog series, let’s recap the three key aspects under consideration for converting from legacy ETL to modern ETL.
There’s recently been an important debate taking place on LinkedIn around the topic of relational databases, joins and how that impacts a user’s experience with analytics.
Almost three years ago today, to the day, Talend opened its fourth global research and development center, and its second one in France, in Nantes. It was clear to Talend from the very beginning of this new innovation center that it would not be a simple satellite of existing centers, but a key element in our strategy and overall R&D efforts.
As analytics software vendors, we need to do something profoundly different to improve how business users access, consume, and interact with data.
When doing data matching with large sets of data, consideration should be given to the combinations that can be generated, and it’s associated effects on performance. This has an effect when using Talend’s Data Integration Matching and Data Quality components. Matching routines do not scale in a linear fashion.
