Best practices for structuring large Laravel applications

As our Laravel application has grown, we've been thinking about how to best structure the codebase to maintain scalability and readability. Here are some practices we've found helpful: 1. Use Domain-Driven Design (DDD): Organize your code into domains based on business capabilities rather than technical layers. 2. Implement Repository Pattern: Create repositories to abstract the data layer and make your code more testable. 3. Use Service Classes: Move business logic out of controllers and into dedicated service classes. 4. Create Value Objects: For domain-specific concepts like Money or Email, create dedicated value objects. 5. Utilize Laravel's Package Development: Extract reusable functionality into packages. 6. Implement CQRS: Separate read and write operations for complex domains. 7. Use Events and Listeners: Decouple components by using Laravel's event system. What structures have you found effective for large Laravel applications? Any patterns that worked particularly well for you?