What is the best way to structure an nservicebus solution? -


we're in process of developing service , hr service purposes of user management, we're having trouble deciding best way structure projects.

one dev believes project , hr project's should separated in subversion , should use svn externals each messages project?

another dev thinks should put them in same subversion project partition services having all.sln, hr.sln, , it.sln splitting them folders.

what best way partition these service boundaries?

i'm not familiar subversion, typically have done have dependencies between services checked source control post build , branched respective service after. reason done allow each service independently decide when take newer version of shared dependency. using branch operation have full history of dependency , can roll @ time. gives ability ship service different versions of same dependency. in subsequent branches of service can have varying versions of dependency.

in case check-in messages assemblies , branch(or merge) them each service. there can take new versions required.


Comments

Popular posts from this blog

asp.net - repeatedly call AddImageUrl(url) to assemble pdf document -

java - Android recognize cell phone with keyboard or not? -

iphone - How would you achieve a LED Scrolling effect? -