Pull to refresh

Comments 1

I totally agree with this guide, I also read at Reddit "

If open-closed and liskov substitution were applied to microservice design, I could see things going horribly wrong.

Open-Closed is typically implemented through inheritance or composition, which are both bad approaches to microservice design if loose coupling and deployability are desired. e.g. If service B is an extension of service A (especially data structures), how do you change service A and deploy it without also deploying service B - or at the very least thoroughly testing it to see the effects? It would be even worse if there was a service C that added functionality to B, and so on.


Only those users with full accounts are able to leave comments. Log in, please.