Hello folks, IOblend here. Hope you are all keeping well.
There is one thing that has been bugging us recently, which led to the writing of this blog. While working on several data projects with some of our clients, we observed instances when data lineage had not been implemented as part of the solutions. In a couple of cases, data lineage was entirely overlooked, which raised our eyebrows.
Data lineage is paramount from the data auditing point of view. How else would you keep track of what is happening to your data throughout its lifecycle? What if your systems go down and the data becomes corrupted? How would you know what data generated spurious results down the line? You will really struggle to restore your data to the correct state if you do not know where the problem is.
The common reason for data lineage omission was the time pressure to deploy a new system. Delivering the system was considered a much higher priority than ensuring the data quality that fed it. We get it, designing and scripting data lineage across your entire dataflows and data estate can be a massive undertaking, especially under time and resource pressure.
However, data issues always come to bite you in the long run. Just from the security and reliability points of view, you absolutely must be on top of your data happenings. Data lineage gives you that ability. The more granular data lineage is, the easier your life will be when things go wrong with your data.
Inevitably, you will have to implement data lineage, but then someone will have to code it from scratch. Data lineage must go all the way across the data from the source to the end point and cover the data at the lowest level regardless of the types. It should be the same granularity for all stakeholders, so everyone works off the base baseline. You will then have a much greater confidence in your data estate.
Implementing data lineage is not a simple job. You need to set and build in data quality and monitoring policies for all dataflows. Depending on your resources, this can be a daunting task. It is much trickier to implement if you are doing live data streaming. There are some tools available on the market that can help you with the task, but you need to make sure they can work well with the rest of your data estate and give you sufficient granularity.
Since we have encountered data lineage issues on more than one occasion, we made data lineage an integral part of our solution. We do DataOps, and data lineage is DataOps. At IOblend, we made sure that the most granular data lineage is available to you ‘out-of-the-box’. It starts at record level with the raw data and maps the transformations all the way to the end target. Our process utilises the power of Apache Spark™ but requires no coding whatsoever on the user’s part. Just visually design your dataflow and data lineage is applied automatically, every time.
Once applied, you can trace data lineage via IOblend or any other analytical tool you may use at your data end points. No hassle. Your data citizens will always have the full confidence in the quality of their data.
IOblend – make you data estate state-of-the-art
Stay safe and catch you soon
Continuous Data Replication for DR and Continuity
Continuous Data Replication: for Business Continuity and DR 📝 Did you know? According to industry studies, the average cost of IT downtime is approximately £4,500 per minute. For a large enterprise, a single hour of data loss or system unavailability can translate into millions in lost revenue, legal penalties, and irreparable brand damage. The Pulse of
Smart Meter Data: Billing to Forecasting
Utilities: Smart Meter Data to Billing and Demand Forecasting 📋 Did You Know? The global roll-out of smart meters generates more data in a single day than most utility companies used to collect in an entire decade. While traditional meters were read once a month, or even once a quarter, smart meters transmit data at intervals
SCADA Streams to Reliability Analytics
Energy: SCADA Streams to Reliability Analytics 🔌 Did you know? The average modern wind turbine or smart substation generates roughly 1 to 2 terabytes of data every month. However, historically, less than 5% of that sensor data was actually used for decision-making. Most of it was simply discarded or “siloed” in SCADA systems, serving as a
Building Live ETA Pipelines for Fleet Operations
Logistics: Live ETA Prediction Pipelines from Fleet + Orders 🚚 Did you know? The “Last Mile” is famously the most expensive and inefficient part of the supply chain, often accounting for up to 53% of total shipping costs. The Evolution of Real-Time Logistics Live ETA (Estimated Time of Arrival) prediction pipelines represent the shift from reactive
DB2 CDC to Lakehouse Without Re-Platforming
From DB2 to Lakehouse: Real-Time CDC Without Re-Platforming 💻 Did you know? Mainframe systems like DB2 still process approximately 30 billion business transactions every single day. Despite the rush toward modern cloud architectures, the world’s most critical financial and logistical data often resides in these “legacy” environments, making them the silent engines of the global economy.
Real-Time Upserts: Deduping and Idempotency
Streaming Upserts Done Right: Deduping and Idempotency at Scale 💻 Did you know? In many high-velocity streaming environments, the “same” event can be sent or processed multiple times due to network retries or distributed system failures. The Art of the Upsert At its core, a streaming upsert (a portmanteau of “update” and “insert”) is the process of synchronising incoming data with an existing
