Laravel Scout Batcher

Database-backed, search-driver-agnostic batching for Laravel Scout.

Scout normally observes each saved or deleted model and immediately performs or queues a corresponding search operation. That can create many small requests to engines that are more efficient with large batches. For example, Meilisearch recommends sending documents in bulk because it handles large batches efficiently and processes each batch as one task.

This package retains Scout's observer and engine APIs, but replaces its queued collection methods with a transactional database outbox. A pending group is processed when either:

• it reaches max_batch_size; or
• its oldest operation has waited debounce_seconds.

The latest operation for each model wins.

Compatibility

• PHP 8.1+
• Laravel 10, 11, 12, or 13
• Laravel Scout 10 or 11
• Any Scout engine implementing the standard update and delete methods

No Redis service is required.

Installation

This package is published on Packagist as jonhassall/laravel-scout-batcher.

composer require jonhassall/laravel-scout-batcher
php artisan vendor:publish --tag=scout-batcher-config
php artisan migrate

Replace Scout's trait on each batched model:

use Illuminate\Database\Eloquent\Model;
use LaravelScoutDebouncer\Concerns\BatchSearchable;

class Product extends Model
{
    use BatchSearchable;
}

Do not use Laravel\Scout\Searchable alongside BatchSearchable; the latter already includes it.

Configuration

Every option in config/scout-batcher.php can be configured through the corresponding environment variable:

schedule.poll_seconds accepts whole-minute intervals expressed in seconds. Laravel's supported sub-minute values (1, 2, 5, 10, 15, 20, or 30) are also available; other values below one minute fall back to once per minute.

Scheduler

The package registers this command with Laravel's scheduler automatically:

php artisan scout-batcher:process

For local development, Laravel's persistent scheduler is convenient:

php artisan schedule:work

To register the schedule yourself, disable schedule.enabled and add:

use Illuminate\Support\Facades\Schedule;

Schedule::command('scout-batcher:process')
    ->everyFiveMinutes()
    ->withoutOverlapping()
    ->onOneServer();

The package schedule uses withoutOverlapping() and onOneServer(). The command also acquires its own atomic lock, so scheduled and manual invocations cannot process concurrently. Set lock_store when the application's default cache is not shared by every application server. lock_seconds must be longer than the longest expected process run. Laravel can poll as often as once per second if your application needs sub-minute processing.

Manual operation

Process all currently pending rows, including under-sized rows whose debounce window has not elapsed:

php artisan scout-batcher:process --force

Limit the number of batches processed in one invocation:

php artisan scout-batcher:process --max-batches=10

Bypassing batching

The normal Scout synchronous methods bypass the outbox:

$product->searchableSync();
$product->unsearchableSync();

The normal methods are debounced:

$product->searchable();
$product->unsearchable();

Disabling scout-batcher.enabled makes the trait delegate to Scout's original queueing behavior.

Retries and failures

Failed batches remain pending and are retried after retry_after_seconds. The pending table records the attempt count and latest error for inspection.

Operational note

When the outbox uses a different database connection from a model, enable Scout's after_commit option so rolled-back model transactions cannot leave pending rows behind.

The package reduces application-to-engine request count, but some engines acknowledge a batch asynchronously. Successful processing means the Scout engine accepted the request, not necessarily that the remote index has finished processing it.

Events

The package dispatches:

• LaravelScoutDebouncer\Events\ScoutBatchProcessed
• LaravelScoutDebouncer\Events\ScoutBatchFailed

How it works

flowchart TD
    A["Your model is saved or deleted"] --> B["The change is added to the pending table"]
    B --> C["More changes to the same model<br/>are combined into one pending operation"]
    C --> D["The scheduled processor runs<br/>with only one worker at a time"]
    D --> E{"Is the batch ready?"}
    E -- No --> F["Wait for more records<br/>or the debounce time"]
    F --> D
    E -- Yes --> G["Load the latest model state"]
    G --> H{"Does the model still exist<br/>and belong in search?"}
    H -- Yes --> I["Send a batched upsert to Scout"]
    H -- No --> J["Send a batched delete to Scout"]
    I --> K{"Did Scout accept the batch?"}
    J --> K
    K -- Yes --> L["Clear the pending operations"]
    K -- No --> M["Keep them pending and retry later"]
    M --> D

Testing

composer install
composer test

License

MIT