java - JMS/REST clients as a centralized library vs one per microservice? -


why microservices architecture mindset see benefit in duplicating rest/jms clients each service has independent code?

does trade-off work out - given comfortability , maintainability of single library/adapter towards server-spec uses abstraction?

what the benefits in practice?

as on brisk of asking opinion, let's answer facts @ hand.

the core thing understand: concept should never seen unalterable law. don't follow rules because rules, because provide helpful guidance regarding design decisions.

in sense balancing. when can abstract common infrastructure elements, good practice avoid code duplication possible.

so instead of creating more , more copies of same class, rather turn "internal library" , have service instances use that. downside here of course all services using library have dependency on it.

coming there, strive provide framework. meaning: base, common parts implemented once - in fashion allows different services configure/extend/enhance framework necessary.


Comments

Popular posts from this blog

html - How to set bootstrap input responsive width? -

javascript - Highchart x and y axes data from json -

javascript - Get js console.log as python variable in QWebView pyqt -