Defeating Race Conditions: Optimistic Locking in Laravel 🛡️

Race Conditions and Lost Updates in High-Concurrency Databases

In complex enterprise applications, multiple users or background jobs often attempt to update the same database record at the same time. This creates a notorious concurrency issue called the Lost Update problem. Imagine an inventory system where Agent A reads a product showing 10 units in stock. Agent B reads the exact same record milliseconds later.

Agent A processes a sale, reducing the stock to 9. Agent B processes another sale based on their initial read of 10, and updates the stock to 9 as well. In a typical Laravel setup, Agent B's UPDATE query simply overwrites Agent A's change, and the database ends up showing 9 items instead of the correct 8. This corrupts inventory data and fails transaction audits.

Optimistic Locking to the Rescue

Smart Tech Devs provides a solution called Optimistic Locking that prevents Lost Updates in high-concurrency environments. It assumes the best-case scenario that users will not overwrite each other's changes. Instead of locking records exclusively (as in pessimistic locking), it allows simultaneous reads and updates. The key is verifying after the UPDATE that no other user modified the data since the initial read.

This approach prioritizes high availability and concurrency over immediate locking, making it ideal for modern web applications.

Implementing Optimistic Locking with PostgreSQL

To achieve this in Laravel, we create a version column in the database schema that increments every time a record is updated. Laravel's Eloquent framework supports this out-of-the-box using an integer version column that auto-increments on updates. However, we prefer enforcing it at the database level for extra security. We define the version column in the migration, set its default to 0, and enable Row Level Security (RLS) on the PostgreSQL database to mathematically guarantee version increments even for raw DB queries.

Simplifying Optimistic Locking in Eloquent Models

To make optimistic locking hassle-free, we create a reusable Eloquent Trait that hooks into the model's saving process. This trait intercepts UPDATE and CREATE actions, checks if the record's version matches the version we read, and throws an exception if it doesn't. If the UPDATE doesn't affect any rows, it means another user modified the record, and we raise a ModelVersionConflictException. The trait automatically updates the current version in memory after a successful update, avoiding future conflicts.

Gracefully Handling Version Conflicts

When a ModelVersionConflictException is thrown, it means the user's action was based on stale data. Rather than returning a generic 500 error, we catch the exception, re-read the fresh data, reapply the user's intended changes, and retry the operation (transparent retries). This ensures a smooth user experience without overwhelming logs or error messages. With Optimistic Locking, we guarantee absolute data integrity even in the most demanding high-concurrency scenarios.