Nothing Runs Until an Action

In a database, when you press run, the query runs. In Spark, when you write a transformation, nothing happens. You can chain a filter onto a select onto a join onto a groupBy, building a description ten lines long, and not a single byte of data has moved. Spark has simply written down what you asked for. The work only begins when you call an action, a special kind of method that demands an actual result: a count, the rows themselves, or a write to disk. This split is called lazy evaluation, and the name fits. A transformation is lazy because it postpones the work; it returns a new DataFrame that remembers the operation but performs none of it. An action is eager: it forces the whole chain of postponed transformations to execute, right now, so it can hand you the result you asked for. Until

About This Interactive Section

This section is part of the Lazy Until You Ask 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 PostgreSQL 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.