Timeline for Placing business logic on a not so small/big project
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 27, 2023 at 11:24 | comment | added | Bernardo Benini Fantin | That's nice to know I can actually mix DDD and MVC. Thanks. | |
| Jul 27, 2023 at 7:39 | comment | added | guillaume31 | MVC and DDD (or rich domain model) are orthogonal. MVC is a presentation layer pattern. A lot of applications use MVC+ a rich domain model or DDD patterns. | |
| Jul 27, 2023 at 7:36 | comment | added | guillaume31 | 1) Having operation-dependent state inside a service blurs the line between service and business model object. It prevents your service from being used in a longer-lived scope such as singleton. The Laravel code samples I could find out there involve stateless services. | |
| Jul 26, 2023 at 17:02 | comment | added | Bernardo Benini Fantin | 1) Why "not ok". 2) It deals with negociations that are made on another platform (Funil) and then registered on my one. 3) CreateNegotiation is a method inside the controller while AcceptNegotiation is a method in the service. 4) It simply updates the record on the DB for that cart (a field that indicates the current step of the cart). And yes, it doest seem weird to finalize the payment transaction, that's kinda my point. Also, I don't know much about DDD, because I work with Laravel and it works as an MVC; but only using MVC seem too "weak" for that. | |
| Jul 26, 2023 at 12:17 | history | answered | guillaume31 | CC BY-SA 4.0 |