[spaetzleesser]

That’s what I am always saying. If you can’t manage libraries you will fail at microservices too, just harder.

I am working on a project right now that was designed as microservices from the start. It’s really hard to change design when every change impacts several independent components. It seems to me that microservices are good for very stable and well understood use cases but evolving a design with microservices can be painful.

[fendy3002]

Especially if in new requirement, microservice A need to interact with service C which originally accessed via B. You can either:

* Make additional changes in B which also takes resources, times and introducing overhead + point of failure, or

* Make A interact directly with C which breaks the boundary