Laravel Lockable Laravel Package

Product Decisions This Supports

• Feature Development: Enables record-level locking for critical workflows (e.g., financial transactions, inventory management, or user-sensitive data) where concurrent edits must be prevented.
• Roadmap Prioritization: Justifies investment in data integrity features for high-risk domains (e.g., healthcare, e-commerce, or compliance-heavy industries).
• Build vs. Buy: Avoids reinventing locking logic (e.g., database-level locks, optimistic/pessimistic concurrency) while maintaining flexibility to integrate with existing auth/permissions systems (e.g., Laravel Nova, Spatie Permissions).
• Use Cases:
  • Multi-user editing conflicts: Prevent race conditions in collaborative tools (e.g., shared documents, project management).
  • Audit trails: Track who locked/unlocked records for compliance or debugging.
  • Temporary holds: Implement "reservation" systems (e.g., hotel bookings, equipment rentals) with expiry-based locks.

When to Consider This Package

Adopt if:

• Your app requires fine-grained record locking beyond Laravel’s native lockForUpdate() (e.g., UI-level locks with expiry, user attribution).
• You use Livewire and need seamless integration with frontend lock indicators (e.g., visual cues for locked rows).
• Your locking logic is reusable across models (traits reduce boilerplate).
• You prioritize MIT-licensed, open-source solutions with minimal dependencies.

Look elsewhere if:

• You need database-agnostic locking (this is SQL-heavy; consider pessimistic-lock or optimistic-lock packages).
• Your use case is short-lived transactions (e.g., <1s operations) where database locks are overkill (use Laravel’s built-in lock()).
• You require distributed locking (e.g., Redis-based; see spatie/laravel-activity-log or spatie/laravel-cache extensions).
• Your team lacks PHP/Laravel expertise to customize traits or handle edge cases (e.g., lock timeouts, deadlocks).

How to Pitch It (Stakeholders)

For Executives: "This package solves a critical gap in our data integrity toolkit by enabling record-level locking—preventing concurrent edits in high-risk workflows (e.g., orders, patient records). It’s a lightweight, MIT-licensed solution that integrates with our existing auth system, reducing the risk of race conditions without heavy custom development. For example, in [Product X], it would let us safely implement [Feature Y], which competitors lack, while keeping costs low."

For Engineering: *"Laravel Lockable provides two traits (Lockable and LockableWithExpiry) to add locking to Eloquent models with minimal setup. Key benefits:

• Traits over interfaces: Easy to adopt incrementally (e.g., add to Order, UserProfile).
• Livewire-friendly: Works with Rappasoft’s tables for UI-level lock indicators.
• Flexible: Supports custom lock scopes (e.g., lockForUser(), lockUntil()) and integrates with any permission system.
• Battle-tested: MIT license, active maintenance (last release: June 2024), and low dependency footprint.

Trade-offs:

• Requires basic SQL knowledge to handle deadlocks/expiry logic.
• Not a silver bullet for distributed systems (but covers 90% of Laravel monolith use cases).

Proposal: Pilot with [Model Z] to validate performance/UX before rolling out to [Critical Workflow A]."*