Jetstream Teams pivot table locking during concurrent membership updates

Laravel Jetstream's Teams feature manages membership through the teams_users pivot table. When multiple administrators concurrently modify team roles or membership status for the same team, the underlying database engine must manage row-level locks to maintain data integrity.

Under high concurrency, these locks can lead to increased request latency as simultaneous updates queue for access to the same records. While standard for InnoDB, the specific impact on Jetstream's Livewire-driven state updates remains an area for optimization.

What is the recommended strategy to mitigate lock contention in the teams_users table during high-frequency concurrent edits? Are there specific database configuration adjustments or application-level queuing patterns that reduce this latency without compromising membership consistency?