Contents
You could move your model classes to a different project/repository and add it as a dependency to your microservices that need to share it. Not sure if your microservices use Swagger, but, you can use Swagger Codegen to generate your models. For example, If you have UserService which accepts and/or returns User object.
Shared libraries (also called dynamic libraries) are linked into the program in two stages. First, during compile time, the linker verifies that all the symbols (again, functions, variables and the like) required by the program, are either linked into the program, or in one of its shared libraries.
How do I share code between microservices?
Instead of coupling your microservices together via common libraries, you can simply isolate and sync any reusable code using the Bit’s ability to isolate and track source code among projects. You can even still install this code with NPM in different repos, and still make changes from any end.
Sharing Code Between Microservices
- Sharing common code between our microservices while keeping our code DRY.
- Avoiding coupling through shared-libs which eliminates the advantages of separating development process.
- Enable simple changes and sync to the code we share between our microservices.
In the shared-database-per-service pattern, the same database is shared by several microservices. This pattern does not reduce dependencies between development teams, and introduces runtime coupling because all microservices share the same database.
How are shared libraries used in microservices applications?
In the application context, sharing means writing code that is compiled against, and requires at runtime, the same library code as another application. By way of example, two applications may both use the same logging library. They may be deployed on separate hosts residing on opposite sides of the globe, but they “share” this library.
Microservices provide increased modularity and separation for your development process. Many services will use the same code, so sharing code between them is critical for your development and maintenance efforts. However, coupling services through shared libs might ruin the point of having multiple different services.
While the “library” concept is similar, the definition of “shared” is quite different. In the application context, sharing means writing code that is compiled against, and requires at runtime, the same library code as another application.
When are shared libraries an issue in application design?
When they create coupling. Specifically with regard to shared libraries in microservices, coupling happens when the use of a library in one application applies strong force on integrating applications to also use the same library and/or platform. When are shared libraries an issue in application design?