Implementing your own code-sharing platform
When finding yourself developing different applications in the same domain you will most likely come across the need for using the same functionality that have already been implemented in another application. However, in a project with many different applications, code repositories, microservices and developers, it is not by any means straight forward to adopt a flexible and efficient code-sharing strategy. In Fortum Oslo Varme (where I operate as tech lead) we have a code-sharing policy of always building reusable code-packages for functionality that are needed by more than one component. This way, it is easy to have control over where the code is located, improve maintainability, reduce errors and the time spent coding, and make it easier to push new features and fixes to all components using the same functionality. We have our own private code registries for our .NET Core and Angular code packages, meaning that we have one NuGet registry and one NPM registry.
Let us start having a look at the overview of our code-sharing platform in the figure below:
