Enterprise Laravel
summary
Argues Laravel is already enterprise-ready and lists concrete practices: stick to Laravel conventions, use native tools to reduce custom maintenance, enforce CI tests and automated linting, shorten time from commit to production, and build good local seeders rather than shipping prod DB dumps. Recommends a thin abstraction over external SDKs, prioritize making instance provisioning fast (make spinning up a new instance trivial), avoid premature microservices, manage technical debt, and apply YAGNI principles (YAGNI — you aren't going to need it).
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:03What is Enterprise?
- 5:52Code considerations
- 13:25Conventions and testing
- 22:06External services and microservices
- 26:16Process and onboarding
- 30:45Hiring and seniority
- 31:07Conclusion
related talks
49mLaravel - If, how and why you should use it!
48mMigrating a 15 Year Old Enterprise Application to Laravel: Lessons Learned and Opportunities Gained
54mThings Laravel Made Me Believe
38mCrafting maintainable Laravel applications
39m50 Laravel Tips
57mThe Laravel Ecosystem
36mLiving peacefully with Laravel
28mProduct in Laravel? No Problem!