Add a comment

 

Re: An architecturally-evident coding style

Thanks Simon good post. On the MongoTweetDao thing, the way I've seen this done (and now it myself) on .Net with a DI container is, that the TweetDao _interface_ belongs to the component, but the Mongo-specific implemention is considered external: call it the wrapper round mongo rather than calling it part of the Tweet component. Maybe you'd feel this falls too far back to the left hand picture of a component spanning 2 layers, but it does show clearly in both code and architecture that the TweetDao interface belongs to the Tweet component. I think the cost of your right hand picture is the cost of testing? How much work/cost has it been to create or maintain a databases for testing compared to the cost of having coded for unit testing.

Re: An architecturally-evident coding style


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).