Re:Give Me Back My Monolith
by barbecue_sauce on Thursday March 14, 2019 @01:23AM
(#19386710)
I would say it depends on the stability of what's being copy/pasted. If it's just boilerplate, it's less concerning.
In my opinion, decoupling should be prioritized over DRYness (within reason). A microservice should be able to live fairly independently from other microservices. While throwing out shared libraries (which can be maintained and distributed independently from services) seems like overkill, it seems much better than having explicit inheritance between microservice projects like the original poster is describing.
Re:Give Me Back My Monolith
by danmaz74 on Thursday March 14, 2019 @05:11AM
(#19387571)
Sure, no problem with boilerplate.
For any non trivial code, which needs to be maintained and be kept well tested, to the contrary of the OP, I would favor shared libraries over copy/paste.
In my opinion, decoupling should be prioritized over DRYness (within reason). A microservice should be able to live fairly independently from other microservices. While throwing out shared libraries (which can be maintained and distributed independently from services) seems like overkill, it seems much better than having explicit inheritance between microservice projects like the original poster is describing.