3 ms·
>Like building out abstractions for adapters and connection points I'm not sure I'm on the same page here but we often use Repository Pattern were abstractions
by konart 5y ago
>Like building out abstractions for adapters and connection points
I'm not sure I'm on the same page here but we often use Repository Pattern were abstractions are needed (obvious example would be some data storage).
We don't have too many libraries in our code. No DDD stuff for sure.
CRUDy apps basically mean you have some domain related structs and a few database methods to connect those structs to data.
- hardwaresofton 5y agoYeah you are -- repository pattern, maybe some built-in serializers/adapters is what I'd expect to be the extent of DDD for most CRUD-y projects. Generally the less libraries/frameworks the better. > CRUDy apps basically mean you have some domain related structs and a few database methods to connect those structs to data. Yup fully agreed here -- I was trying to see if there were cases where they poster had to build the abstractions you'd want for a DDD-like system. Normally you don't have to so I was wondering if their experience matched up with my ideas about DDD to start with.