<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Data-Engineering on Sohil Ladhani Blog</title><link>https://sohilladhani.com/blog/tags/data-engineering/</link><description>Recent content in Data-Engineering on Sohil Ladhani Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 20 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sohilladhani.com/blog/tags/data-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>Backfill and Reprocessing</title><link>https://sohilladhani.com/blog/post/2026-06-20-backfill-and-reprocessing/</link><pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate><guid>https://sohilladhani.com/blog/post/2026-06-20-backfill-and-reprocessing/</guid><description>You add a new derived field to your user profiles: &amp;ldquo;days since last purchase.&amp;rdquo; You can compute it for new events going forward. But existing users already have purchase history. You need to compute this field for all existing users retroactively. That&amp;rsquo;s a backfill.
Backfills happen constantly in production systems. They&amp;rsquo;re more disruptive than they look.
The Basic Problem You have a dataset of 500 million user records. You need to reprocess all of them to compute the new field.</description></item></channel></rss>