Skip to main content

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.

2
  • There is an import point you are making here that I think needs to be called out explicitly - that the primary way to share code between multiple projects is that you have to create yet another binary - which incurs the cost of binary dependency management - this is not a cost that has to be paid if you have a monolith (that compiles to a single binary). Commented Oct 19, 2023 at 22:26
  • Yes, everything is hunky-dory if you have a monolith - except, of course, that you have a monolith. The last thing I worked on had 37 separate runnable applications and dozens upon dozens of supporting "assemblies" (the .NET equivalent of Java packages) all bound together into a single git repo and a single Visual Studio solution. That's a much different dependency management problem. Commented Oct 19, 2023 at 22:53