Laravel multitenancy on Octane without leaking PDOs

Short summary

Laravel's naive multitenancy pattern leaks PDOs or burns expensive connection handshakes on Octane because the DatabaseManager persists across requests. The fix uses a per-worker LRU cache with credential fingerprints and connection aliasing via reflection to reuse pooled connections safely. This eliminates both security vulnerabilities and the tens-of-milliseconds handshake overhead per request.

• •Octane's persistent container breaks FPM-era multitenancy patterns, causing PDO leaks or expensive reconnects
• •Solution: per-worker LRU cache with connection aliasing to reuse pooled databases without security gaps
• •Real-world optimization saving tens of milliseconds per request and eliminating isolation vulnerabilities

Generated with AI, which can make mistakes.