Skip to main content
10 events
when toggle format what by license comment
Jun 3, 2016 at 2:22 history tweeted twitter.com/StackProgrammer/status/738556475941998592
May 23, 2016 at 16:55 vote accept Anchor
May 23, 2016 at 14:52 comment added JeffO Have you considered an ORM?
May 22, 2016 at 23:34 comment added Anchor I don’t know, maybe there are some better ways of exposing functionality without explicitly defining an interface around it, maybe using things like dependency injection and variadic arguments with sane defaults; where the functionality is there if you need it, but hidden if not. Not sure if that’’s a DDD anti-pattern or not though.
May 22, 2016 at 23:32 comment added Anchor Some measure of reusability across domains would be nice, but my main goal is to encapsulate persistence to reduce coupling across concerns as much as possible. But i'm conflicted because the more database functionality gets exposed, the tighter the coupling becomes until the higher layers of abstraction pretty much have full knowledge of the underlying implementation details. Now that I think about both of your questions a bit more, the gist of it is that I want to have my cake and eat it too... I guess what I'm looking for is a good compromise somewhere in between.
May 22, 2016 at 19:05 answer added Christophe timeline score: 5
May 22, 2016 at 18:01 comment added hyc Since most databases offer disjoint functionality, if you want a general abstraction you're going to be stuck with the lowest common denominator. What do you actually need to accomplish?
May 22, 2016 at 17:10 comment added Thomas Junk Are you doing the abstraction as a framework and are looking for reusablity or do you have a concrete application (domain)?
May 22, 2016 at 15:49 review First posts
May 27, 2016 at 15:24
May 22, 2016 at 15:46 history asked Anchor CC BY-SA 3.0