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.
Regarding the code duplication, I have seen this happening in microservice projects. And of course it comes with all the disadvantages of duplicated code. Even if you would extract out some common business functionality into a library you still need to upgrade this lib and every service that consumes it when a change happens.
Of course some experts say that this is down to poor cutting / design of the services themselves. I guess it is a topic of theory vs. real world.
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.