When developing multiple microservices, we see a lot of duplicate code, cross-cutting concerns and non-functional code. This makes some good reasons to set up a shared library. Setting up a shared library often takes more time and attention than just moving code. It includes dependencies, configuration, properties and tests. If you don’t set this up correctly; ‘your shared library are ill’.
What should you keep in mind when developing a shared library? Would it be a good idea to create a shared library in the first place? What belongs and what doesn’t belong in a shared library?
During this presentation I discuss 5 ‘habits’ for developing an effective shared library. With practical examples that you can apply directly within your project tomorrow. You can use the examples to take your shared library to a higher level.
Willem Cheizoo, JDriven
Recorded at Jfokus 2023 in Stockholm 8th of february
http://www.jfokus.se