Finding lost features - How NOT to build mazes and complexity

On Conferences, we learn about DDD, Hexagonal Architecture or CQRS. Naturally, when we come back to work, we want to use these methodologies and practices which often results in just having “DTO”, “Repository”, “ValueObject” or even “CQRS” directories in our code… This is a very technical separation of namespaces and code in general, which doesn’t help in finding what exactly is implemented in our system. In my presentation, I will show how I deal with separating features and how we, as an Engineering Team, can implement clearly business requirements in systems that are not handling Facbook-scale traffic.

Transcript

1. Finding Lost Features Konrad Alfaro @ How NOT to build mazes and complexity Entity Controller Service CQRS
2. Who am I? 🤔 Backend Engineer with 8+ years of experience 🤓 Solutions Architect & Consultant @ 8lines.team 👔 Software Agencies, Product companies, Enterprises 🔨 Built 2 Startups (and failed) 😰 8lines.team
3. 8lines.team Scenario 🎬
4. 8lines.team • Given the system is a CRM system with Documents and Clients module • Given the resources in the CRM system are mostly CRUDs • Given the system is going to be used very infrequently by limited amount of users
5. 8lines.team • When we to add an electronic signature process to our Document resource
6. 8lines.team Then…
7. 8lines.team I don’t know where to start 😱
9. What’s the most important in Software Development? 8lines.team
10. Framework! 8lines.team
12. “Laravel way” 🧙 8lines.team
16. “Symfony way” 🎻 8lines.team
20. 8lines.team
21. Controller
22. Service
23. Event Listener
24. 8lines.team
26. Pros ✅ 8lines.team
27. 8lines.team ✅ We comply with the Framework ✅ We follow standardised rules ✅ We (should) deliver fast ✅ It is good enough
28. Drawbacks ⚠ 8lines.team
29. 8lines.team ⚠ We hide business logic behind Framework concepts and rules ⚠ We couple our business logic strictly with 
 the Framework
30. 8lines.team Takeaways 🍕
31. Framework is not your friend, it’s just a tool you can use 8lines.team
32. 8lines.team It’s too hard to f ind anything 😑
33. 8lines.team
34. DDD 8lines.io Psst, hey you kids. Wanna build some Domain Aggregates?
35. Directory Driven Design 8lines.team
36. 8lines.team
37. Command Handler
38. 8lines.team Message Handler
39. Pros ✅ 8lines.team
40. 8lines.team ✅ We think about our business Domain ✅ We have better separation of concerns
41. Drawbacks ⚠ 8lines.team
42. 8lines.team ⚠ We introduce a lot of (most likely) unnecessary complexity - it is just a CRUD! ⚠ We like to implement new patterns just after one conference talk 😉
43. 8lines.team
44. Takeaways 🍕 8lines.team
45. 8lines.team Don’t be an immature developer Pick proper solutions to your problems
46. 8lines.team You don’t work at Facebook* 🙃 * - Unless you do 😅
47. 8lines.team
48. Repository overview
50. Pros ✅ 8lines.team
51. 8lines.team
52. 8lines.team • Given the system is a CRM system with Documents and Clients module • Given the resources in the CRM system are mostly CRUDs • Given the system is going to be used very infrequently by limited amount of users
53. 8lines.team • Given the system is a CRM system with Documents and Clients module • Given the resources in the CRM system are mostly CRUDs • Given the system is going to be used very infrequently by limited amount of users
54. Cons ⚠ 8lines.team
55. 8lines.team ⚠ Hard to implement and maintain ⚠ We introduce a lot of complexity
56. 8lines.team
57. Takeaways 🍕 8lines.team
58. Find fun 🎢 in building solutions, Instead of trying a new frameworks 8lines.team
59. 8lines.io
60. There is hope! 8lines.team
64. Processor
65. Modi f ier
66. Modi f ier
67. Modi f ier
68. Action
74. Infrastructure
75. Drawbacks ⚠ 8lines.team
76. 8lines.team ⚠ This is not a Domain-Driven approach ⚠ It is not suitable for large and complex systems
77. Pros ✅ 8lines.team
78. 8lines.team ✅ We introduce separation of business concerns ✅ We don’t required everyone to be a DDD expert ✅ We deliver fast features using suitable concepts
79. 8lines.team • Given the system is a CRM system with Documents and Clients module • Given the resources in the CRM system are mostly CRUDs • Given the system is going to be used very infrequently by limited amount of users
80. 8lines.team • Given the system is a CRM system with Documents and Clients module • Given the resources in the CRM system are mostly CRUDs • Given the system is going to be used very infrequently by limited amount of users
81. Takeaways 🍕 8lines.team
82. Make your systems yours 8lines.team
83. 8lines.team ✅ Framework is not your friend ✅ Don’t be immature and hype-driven ✅ Build solutions, not personal playgrounds ✅ Make your systems readable for you
84. Thanks! 🙌 konradalfaro.com 🌍 8lines.team @alfaro_konrad