@stilkov Wasn’t there an entire chapter about abstracting away technical details and strategic design?
1
@kellabyte @stilkov that's not how I've read it. It says that the model is more important. Learn it first and pick the db later
4
1
3
@jeppec @kellabyte I agree – my reading is it advocates separation of concerns from a modeling perspective. Uncle Bob’s take is different.
2
@kellabyte @stilkov yes - it's for integrating with another system. I.e. Not something you use internally to abstract away the db
5
@kellabyte @stilkov of course it cannot, thats also not what the pattern says. I feel like you WANT to misread the intentions?
2
@kellabyte @jeppec It’s a very common thing, e.g. when you build an adapter to various different external accounting systems.
3
@kellabyte Then taken to the extreme, what you’re saying is there can be no isolation between connected systems *at all*. @jeppec
Oct 19, 2015 · 6:06 AM UTC
2
1


