Product in Laravel? No Problem!
summary
A concrete Laravel architecture for multi-tenant production: use the Spy Laravel Multitenancy package for tenant context, apply a Global Scope to filter queries, store per-tenant config with config:set, and pass the tenant into Artisan commands and jobs. Compare single-database vs multi-database (multi-db gives better scalability but harder provisioning), prefer Redis for cache and queues (avoid file driver), use chunked uploads for large files and Laravel encryption for sensitive data, and use tools like Laravel Shift plus OSS packages such as Magic Login and markable to speed migrations and add functionality.
AI-written summary · about
chapters (12)
- 0:00Product goals and SaaS
- 3:15Multitenancy in Laravel
- 5:47DDD and packages structure
- 8:59Cache files for scalable APIs
- 11:14Security attacks and GDPR
- 13:04Performance and scalability
- 15:37Code quality and updates
- 18:06Summary open source packages
- 19:12Q&A GDPR and tenancy
- 21:22Q&A Laravel Shift tenancy
- 23:29Q&A Subscription features
- 24:54Q&A Multi vs single database
related talks
24mImplementing multi-tenancy in a Laravel app
39mBuilding a multi-tenant SaaS with PHP and Laravel in 2025
49mLaravel - If, how and why you should use it!
33mEnterprise Laravel
30mLegacy to Laravel in 30 minutes
57mThe Laravel Ecosystem
25mLess Pain with Gain, how Laravel helps you scale your Applications
39mThe State of Laravel