Symfony Tips

Quick and practical tricks to develop solid backend systems

1. Symfony Tips #01 - One Use Case → One Controller
2. Symfony Tips #02 - Use folders to group your Use Cases
3. Symfony Tips #03 - Move internal dependencies to the constructor
4. Symfony Tips #04 - Use Repositories
5. Symfony Tips #05 - One line per service
6. Symfony Tips #06 - Decode input in an Event Subscriber
7. Symfony Tips #07 - Serialize output in an Event Subscriber
8. Symfony Tips #08 - Flush in an Event Subscriber
9. Symfony Tips #09 - Catch exceptions in an Event Subscriber
10. Symfony Tips #10 - Test your Controllers
11. Symfony Tips #11 - Use Uuids as identifiers
12. Symfony Tips #12 - Move all business logic to your entities
13. Symfony Tips #13 - Do validation in your setters
14. Symfony Tips #14 - Separate your application in modules
15. Symfony Tips #15 - Dispatch Domain Events
16. Symfony Tips #16 - Send emails asynchronously
17. Symfony Tips #17 - Store your Domain Events
18. Symfony Tips #18 - Expose a Domain Events API
19. Symfony Tips #19 - CQRS - Command Bus
20. Symfony Tips #20 - CQRS - Query Bus
21. Symfony Tips #21 - CQRS - Event Bus
22. Symfony Tips #22 - CQRS - Projections