Job chaining and batching in Laravel - Mini Project: Build & Apply

Job chaining and batching in Laravel

📖 Scenario: You are building a Laravel application that processes user data in steps. You want to run jobs one after another (chaining) and also run a group of jobs together (batching) to handle tasks efficiently.

🎯 Goal: Build a Laravel job chaining and batching setup that runs three jobs in sequence and groups them into a batch.

📋 What You'll Learn

Create three Laravel job classes named FirstJob, SecondJob, and ThirdJob.

Create a job batch that contains these three jobs.

Chain the jobs so that SecondJob runs after FirstJob, and ThirdJob runs after SecondJob.

Dispatch the batch with the chained jobs.

💡 Why This Matters

🌍 Real World

Job chaining and batching help run multiple background tasks in order and as a group, such as sending emails, processing files, or updating records.

💼 Career

Understanding Laravel job chaining and batching is important for backend developers to build efficient, scalable queue-based systems.

1

Create the three job classes

Create three Laravel job classes named FirstJob, SecondJob, and ThirdJob using the php artisan make:job command or by defining empty classes that implement ShouldQueue.

Laravel

// Create three job classes: FirstJob, SecondJob, ThirdJob
// Your code here

Hint

Use the php artisan make:job JobName --queued command or create classes that implement ShouldQueue with the required traits.

2

Create a batch variable with the three jobs

Create a variable called $batch that uses Bus::batch() to create a batch containing new instances of FirstJob, SecondJob, and ThirdJob.

Laravel

<?php

// Create a batch variable called $batch with the three jobs inside Bus::batch([])
// Your code here

Hint

Use Bus::batch([new FirstJob(), new SecondJob(), new ThirdJob()]) and assign it to $batch.

3

Chain the jobs in the batch

Modify the batch creation so that SecondJob runs after FirstJob, and ThirdJob runs after SecondJob by using the chain() method inside Bus::batch().

Laravel

<?php

// Chain the jobs so SecondJob runs after FirstJob, and ThirdJob runs after SecondJob
// Your code here

Hint

Use Bus::batch([new FirstJob()])->chain([new SecondJob(), new ThirdJob()])->dispatch() to chain jobs.

4

Dispatch the batch with chained jobs

Ensure the batch with chained jobs is dispatched by calling dispatch() at the end of the batch and chain setup.

Laravel

<?php

// Confirm the batch is dispatched with the chained jobs
// Your code here

Hint

Make sure to call dispatch() at the end to start the batch with chained jobs.

Practice

1. What is the main difference between job chaining and job batching in Laravel?

easy

A. Job chaining is for database tasks only; job batching is for email tasks only.

B. Job chaining runs jobs in parallel; job batching runs jobs sequentially.

C. Job chaining runs jobs one after another; job batching runs jobs together and tracks progress.

D. Job chaining requires manual tracking; job batching does not track progress.

Solution

1. Step 1: Understand job chaining

   Job chaining runs jobs one after another in a specific order.

2. Step 2: Understand job batching

   Job batching runs many jobs together and tracks their progress as a group.

3. Final Answer:

   Job chaining runs jobs one after another; job batching runs jobs together and tracks progress. -> Option C

4. Quick Check:

   Job chaining = sequential, Job batching = grouped with progress [OK]

Hint: Chaining = sequence; batching = group with progress tracking [OK]

Common Mistakes:

• Confusing parallel and sequential execution
• Thinking batching runs jobs one by one
• Assuming chaining tracks progress automatically

2. Which of the following is the correct syntax to chain two jobs JobA and JobB in Laravel?

easy

A. JobA::chain([new JobB])->dispatch();

B. JobA::dispatch()->chain([JobB]);

C. dispatch(new JobA)->chain(new JobB);

D. dispatch(new JobA)->chain([new JobB]);

Solution

1. Step 1: Recall chaining syntax

   In Laravel, chaining jobs uses dispatch(new JobA)->chain([new JobB]).

2. Step 2: Check options for correct method calls

   dispatch(new JobA)->chain([new JobB]); matches the correct syntax with dispatch(new JobA)->chain([new JobB]);.

3. Final Answer:

   dispatch(new JobA)->chain([new JobB]); -> Option D

4. Quick Check:

   dispatch + chain array = correct chaining syntax [OK]

Hint: Use dispatch(new Job)->chain([jobs]) for chaining [OK]

Common Mistakes:

• Calling chain() on the job class instead of dispatch
• Passing a single job without array to chain()
• Using incorrect method order

3. Given the following code, what will be the output in the logs if all jobs succeed?

Bus::batch([
    new Job1(),
    new Job2(),
    new Job3()
])->then(function () {
    Log::info('Batch completed successfully');
})->dispatch();

medium

A. Logs 'Batch completed successfully' immediately after dispatch.

B. Logs 'Batch completed successfully' after all jobs finish.

C. No logs will be created because then() is not supported.

D. Logs 'Batch failed' if any job fails.

Solution

1. Step 1: Understand batch then() callback

   The then() callback runs after all jobs in the batch succeed.

2. Step 2: Analyze the code behavior

   Since all jobs succeed, the callback logs 'Batch completed successfully' after finishing.

3. Final Answer:

   Logs 'Batch completed successfully' after all jobs finish. -> Option B

4. Quick Check:

   Batch then() runs after success [OK]

Hint: then() runs after all batch jobs succeed [OK]

Common Mistakes:

• Thinking then() runs immediately after dispatch
• Assuming then() runs on failure
• Believing no logs are created

4. Identify the error in this job chaining code:

dispatch(new JobA)->chain(new JobB);

medium

A. chain() expects an array of jobs, not a single job instance.

B. dispatch() cannot be used with chaining.

C. JobB must be dispatched separately before chaining.

D. JobA must be a queued job class, not a job instance.

Solution

1. Step 1: Check chain() parameter requirements

   The chain() method requires an array of job instances.

2. Step 2: Analyze the code

   The code passes a single job instance new JobB without wrapping it in an array.

3. Final Answer:

   chain() expects an array of jobs, not a single job instance. -> Option A

4. Quick Check:

   chain() needs array of jobs [OK]

Hint: Always pass an array to chain(), even for one job [OK]

Common Mistakes:

• Passing a single job without array to chain()
• Trying to dispatch chained jobs separately
• Confusing dispatch and chain usage

5. You want to run three jobs JobX, JobY, and JobZ where JobY should only run after JobX completes, but JobZ can run anytime in parallel. Which Laravel approach correctly handles this?

hard

A. Use job chaining for JobX and JobY, and dispatch JobZ separately.

B. Use job batching for all three jobs together.

C. Chain JobX, JobY, and JobZ in one chain to run sequentially.

D. Dispatch all three jobs separately without chaining or batching.

Solution

1. Step 1: Understand job dependencies

   JobY depends on JobX finishing first, so they must run sequentially.

2. Step 2: Consider JobZ's independence

   JobZ can run anytime, so it should run separately in parallel.

3. Step 3: Choose correct Laravel approach

   Use chaining for JobX and JobY, and dispatch JobZ separately to run in parallel.

4. Final Answer:

   Use job chaining for JobX and JobY, and dispatch JobZ separately. -> Option A

5. Quick Check:

   Chain dependent jobs, dispatch independent jobs separately [OK]

Hint: Chain dependent jobs; dispatch independent jobs separately [OK]

Common Mistakes:

• Batching all jobs when order matters only for some
• Chaining all jobs forcing sequential run
• Ignoring job dependencies