This document discusses using a command bus pattern to move code from controllers to handlers. It recommends implementing the Tactician command bus with Symfony to create thin controllers that delegate tasks to specialized handlers. Various middleware plugins are described, such as logging, transactions, and validation middleware, that can be registered to intercept and process commands. The document provides resources for learning more about command buses and Tactician.

1. Command bus
In practice
Marcin Hawraniak

2. About me
●
●
●
●

3. Disclaimer
●
●
●

4. Command Bus - why?
From ...

6. To...

9. HandlerCommand

11. Moving code from
Controller
To
Handler

13. Thin Controller

14. Command Bus - How?

15. Implementations

16. Implementations

17. Tactitian + Symfony

18. Getting started

19. Thin Controller

21. Single Responsibility

22. Handler
Command
Command Bus

25. Tactitian plugins - Custom Middlewares

26. Logging Middleware

28. Logging - assumptions

29. Logging - notes

31. Transaction Middleware

32. Transactions Middleware

33. Locker Class per Command

34. Locking Middleware - notes

36. Validation Middleware

38. Validation Middleware

39. Our handler - extracting validation

41. Validator Class per Command

43. Register middlewares

44. That handler...

47. Event Dispatcher

48. Event Dispatcher

54. Adding new Command

56. Other
●
●
●
●
●

57. Summary

59. Summary
●
●
●
●

60. Resources
● https://tactician.thephpleague.com/
● https://github.com/thephpleague/tactician-bundle
● https://matthiasnoback.nl/2015/01/a-wave-of-command-buses/
● http://symfony.com/app.php/doc/current/create_framework/event_dispatcher.html

61. Questions?
●
●

62. Thank you <3