tag:blogger.com,1999:blog-6709047859447954829.post7972012481432712163..comments2022-04-11T12:36:09.723+01:00Comments on Jan vs. Machine: A case of unwanted separationUnknownnoreply@blogger.comBlogger3125tag:blogger.com,1999:blog-6709047859447954829.post-33240216672855081742016-09-20T20:16:34.428+01:002016-09-20T20:16:34.428+01:00This sounds like a CQRS pattern. More on Martin Fo...This sounds like a CQRS pattern. More on Martin Fowler's blog: http://martinfowler.com/bliki/CQRS.html<br /><br />Not always good, but has it's own advantages sometimes.<br /><br />Cheers,<br />Nemanja<br /><br />www.entarchs.com<br />Unknownhttps://www.blogger.com/profile/03167534439535685512noreply@blogger.comtag:blogger.com,1999:blog-6709047859447954829.post-90469673994215372222016-09-07T15:17:01.741+01:002016-09-07T15:17:01.741+01:00Thanks, that's really interesting to hear. I&#...Thanks, that's really interesting to hear. I've done the same as what you describe, but in my case with Scala, so using sbt for build management.Janhttps://www.blogger.com/profile/01265636364924145888noreply@blogger.comtag:blogger.com,1999:blog-6709047859447954829.post-36578626182204476672016-09-07T01:37:21.131+01:002016-09-07T01:37:21.131+01:00Good post. See this all the time.
I recently tac...Good post. See this all the time.<br /><br />I recently tackled this by including a logical services micro services in the same repository, a VS solution per micro services, and common libs such as the domain model shared via nuget packages using a private feed. All common libs and microservices used semver for versions internally to track compatibility. Works pretty well, allows some isolation between the micro services and can patch a common lib for one microservices without immediately needing to push the change to another.<br /><br />Cheers.BotHeadhttps://www.blogger.com/profile/01709502105796233107noreply@blogger.com