News for hackers. Stuff that matters.
Re:The Cracking Monolith: Forces That Call for Microservices by pathsjs on Wednesday March 22, 2017 @07:03AM (#13929942)
I think you mean that usually testing monoliths is easier (no network and so on) but I am not sure, can you clarify?
Re:The Cracking Monolith: Forces That Call for Microservices by gregmac on Wednesday March 22, 2017 @09:51AM (#13930840)
It should -- microservices require testing versioned interactions between services.

Let's say you're changing the behaviour of a feature in service A that is consumed by service B.

Service A is at version 15, service B is at version 42. You have to deploy service A version, but it has to have the new change but still also be compatible with service B v42 (because that's what's running). Then, when service B v43 is deployed, service A has to start serving the new functionality.

This gets exponentially more complicated with more services, more dependencies and more versions.