Atomic Database Transactions in Laravel

Why Transactions Matter

Consider creating a project and assigning default onboarding tasks. If an exception occurs after creating the project but before creating the tasks, orphaned data remains in the database.

A transaction guarantees all-or-nothing atomicity:

use Illuminate\Support\Facades\DB;

DB::transaction(function () use ($user, $projectData, $defaultTasks) {
    $project = $user->projects()->create($projectData);

    foreach ($defaultTasks as $task) {
        $project->tasks()->create($task);
    }

    return $project;
});

If any line throws a Throwable, Laravel immediately rolls back all changes made during the closure.