Checkpointing

Concepts covered: paStreamProcessing

When a streaming query restarts, everything in memory is gone: the driver that was pacing the loop, the executors that were mid-task, the engine's knowledge of which offsets it had processed. If that knowledge lived only in memory, a restarted stream would face two bad options: start from the beginning of the source and reprocess everything, or start from the end and silently skip whatever arrived during the outage. The checkpoint is the third option: a durable record of the stream's position, written to reliable storage as the stream runs, so a restart resumes exactly where the crash interrupted. The checkpointLocation you set on writeStream in the beginner tier points at a directory, and its contents are worth knowing by name because you will one day inspect them during an incident. The

About This Interactive Section

This section is part of the Structured Streaming: Intermediate lesson on DataDriven, a free data engineering interview prep platform. Each section includes explanations, worked examples, and hands-on code challenges that execute in real time. SQL queries run against a live database. Python runs in a sandboxed Docker container. Data modeling problems validate against interactive schema canvases. All content is framed around what data engineering interviewers actually test at companies like Meta, Google, Amazon, Netflix, Stripe, and Databricks.

How DataDriven Lessons Work

DataDriven combines four interview rounds (SQL, Python, Data Modeling, Pipeline Architecture) with adaptive difficulty and spaced repetition. Easy problems get harder as you improve. Weak concepts resurface until you master them. Your readiness score tracks progress across every topic interviewers test. Every lesson section ends with problems you solve by writing and running real code, not by picking multiple-choice answers.