Nice article. I'm new to micro-services, and I've never develop on a micro-service. However, I'm under the impression that micro-services, in a way, might lead to violate the DRY principle... Since the services are separated, some concerns are the same however, it seems to me that it might lead to some code that will be the same (or very very similar) between the different services' source code... Or am I missing something ? EDIT: but I guess it depends at which level the separation of services is done.
Duplication is accepted and expected in µservices.
Although nothing is stopping you from publishing libraries for the common code. A purist would scoff at this though since they would say you should just have a µservice that performs this common operation.
2
u/CrommVardek Dec 12 '19
Nice article. I'm new to micro-services, and I've never develop on a micro-service. However, I'm under the impression that micro-services, in a way, might lead to violate the DRY principle... Since the services are separated, some concerns are the same however, it seems to me that it might lead to some code that will be the same (or very very similar) between the different services' source code... Or am I missing something ? EDIT: but I guess it depends at which level the separation of services is done.