Timeline for Where perform mapping in strict Domain-Driven Design?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 13, 2024 at 19:36 | comment | added | Ewan | It pushes logic to the application rather than the API, so if you have a web app you might want a BFF to do View Model -> Domain Model. But you should be able to pass your domain objects around without concern. | |
| Aug 13, 2024 at 12:52 | comment | added | Greg Burghardt | I've had problems mapping incoming requests to domain models. It works OK for simple use cases, but things run afoul when you need to validate user input or limit the information that can be manipulated in the request. Honestly, I absolutely do not recommend this for security reasons. Mapping from database to domain model is my preferred approach, though. | |
| Aug 12, 2024 at 20:51 | comment | added | Ewan | how does that make it "unstable"? | |
| Aug 12, 2024 at 18:05 | comment | added | Gman | Isn't it a problem that the domain model is now exposed through the API, making it very unstable? | |
| Aug 12, 2024 at 17:25 | history | edited | Ewan | CC BY-SA 4.0 | added 97 characters in body |
| Aug 12, 2024 at 17:19 | history | answered | Ewan | CC BY-SA 4.0 |