The lucid architecture for building scalable applications
summary
Lucid is a Laravel 5.3–native architecture that turns each user capability into a feature class which runs small, single‑purpose job steps kept in domain folders; controllers become one‑line routers, services separate website/API/back‑end behavior, and jobs stay reusable and queueable. Vine Lab reports one and a half years of use by four back‑end developers with no structural changes, a CLI generator and console insights, and explicit rules (no jobs calling jobs, domains isolated) aimed at reducing legacy and improving testability.
AI-written summary · about
chapters (21)
- 0:00Start
- 0:50The Lucid Architecture
- 2:08Dna Structure
- 4:46Why Would We Have Architectures
- 5:00Three Reasons Why You Would Have an Architecture
- 6:29Eradicate Homelessness of Code
- 9:07Request Response Lifecycle
- 10:54Technical Depth
- 11:15Legacy Code
- 15:23Components of Lucid
- 17:49Dispatcher
- 18:43Jobs
- 19:14Create an Article
- 22:37Service
- 27:40Data
- 31:49Insights Dashboard
- 36:00Questions
- 36:17Is It Possible To Dispatch Job inside the Job
- 37:07Unit Testing
- 42:21Is It Possible To Run a Feature from the Console
- 43:10Validation Step Should Be in the Controllers
related talks
32mFull stack architecture
40mEngineering Complex Applications with Laravel 4
58mDesigning for change with Vertical Slice Architecture
38mCrafting maintainable Laravel applications
28mManaging a team building a modular monolith in Laravel
30mThe working Architecture of Node.js Applications
33mLona: Scaling Server-driven UI
36mStatamic for Laravel devs