Why shared libraries between microservices are bad? [closed]

by

The evils of too much coupling between services are far worse than the problems caused by code duplication

The author is very unspecific when he uses the generic word “coupling”. I would agree with certain types of coupling being a strict no-no (like sharing databases or using internal interfaces). However the use of common libraries is not one of those. For example if you develop two micro services using golang you already have a shared dependency (towards golang’s basic libraries). The same applies to libraries that you develop yourself for sharing purpose. Just pay attention to the following points:

  • Treat libraries that are shared like you would dependencies to 3rd party entities.
  • Make sure each component / library / service has a distinct business purpose.
  • Version them correctly and leave the decision which version of the library to use to the corresponding micro service teams.
  • Set up responsibilities for development and testing of shared libraries separately from the micro services teams.

Don’t forget – The microservices architectural style is not so much focusing on code organization or internal design patterns, but on the larger organizational and process relevant aspects to allow scaling application architectures, organizations and deployments. See this answer for an overview.

More Related Contents:

  1. Usage of interface in Go
  2. Microservices with shared database? using multiple ORM’s? [closed]
  3. Transactions across REST microservices?
  4. Implementing TypeScript interface with bare function signature plus other fields
  5. Microservices – best practices to retrieve the related data to specific user from the other micro services with the minimal memory/time loss
  6. Extend interface defined in .d.ts file
  7. Is it possible to inject interface with angular2?
  8. Easiest way to install Python dependencies on Spark executor nodes?
  9. Microservice Authentication strategy
  10. Explanation of checking if value implements interface
  11. Difference between Fortran’s “abstract” and “normal” interfaces
  12. How to add additional libraries to Visual Studio project?
  13. The difference between the Runnable and Callable interfaces in Java
  14. Advantage of creating a generic repository vs. specific repository for each object?
  15. Is there any ready-made calendar control for iPhone apps? [closed]
  16. Why can’t I declare static methods in an interface?
  17. python pip specify a library directory and an include directory
  18. TextWatcher for more than one EditText
  19. Setting the source IP for a UDP socket
  20. NOT using repository pattern, use the ORM as is (EF)
  21. Elegantly call C++ from C
  22. How exactly does the Spring BeanPostProcessor work?
  23. how to embed an angular app into another app?
  24. NotSerializableException on anonymous class
  25. Responsibilities and use of Service and DAO Layers
  26. Finding the Concrete Type behind an Interface instance
  27. Testing os.Exit scenarios in Go with coverage information (coveralls.io/Goveralls)
  28. Why are C# interface methods not declared abstract or virtual?
  29. dma vs interrupt-driven i/o
  30. Load 32-bit shared library from 64-bit application?

Leave a Comment