Timeline for How can you separate a monolith into domain-driven libraries without duplicating interfaces and still keep dependencies simple?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 6, 2016 at 19:55 | vote | accept | ricksmt | ||
| May 6, 2016 at 19:30 | comment | added | ricksmt | It would be for adapting between domain library interfaces. Perhaps facade is what I really mean/want. I'd hate for that to be a burden on the end application when I'm anticipating the usage. | |
| May 6, 2016 at 19:15 | comment | added | Price Jones | It would be difficult for me to elaborate on the specific use of adapters without more knowledge of your design. ...I think you might be interested in them because you see the possibility of adapting your monolithic objects to the finer tuned interfaces of a divided domain model. If that is what you are thinking, then you would still want to consider whether it is wise to keep all your monolith logic monolithic and try to adapt it to different domains, rather than breaking it up. It is a decision only you can make. | |
| May 6, 2016 at 18:33 | comment | added | ricksmt | I think this is my answer. @Darien mentioned adapters, and I'm thinking I'll need to research that topic to understand how the full solution works. If you want to elaborate on that in part II of your question, that'd make me happy. | |
| May 6, 2016 at 18:28 | history | answered | Price Jones | CC BY-SA 3.0 |