Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • +1 agree to most everything here. Great write up! Commented Jan 31, 2020 at 5:19
  • 1
    Depending on what code actually lives in that "common" project, the benefits of having it pulled out vastly outweigh the risks. Think of all the things you have consumed as NuGet packages before. Imagine the hassle if that code was implemented in every single service instead of a shared package? What I would recommend here is that the "common" project should be used/treated exactly as a "company private" NuGet package. Share it the same way you share 3rd party code, because to your individual services it should be treated as 3rd party library. Commented Jan 31, 2020 at 5:26
  • 1
    @Caleb Yeah, I think you are right... can't get very far without some kind of library. I think I was spooked by the OP's first bullet. I've revised my answer. Commented Jan 31, 2020 at 20:26