Re:Microservices – Combinatorial Explosion of Versions
by hinkley on Thursday March 05, 2020 @03:35PM
(#22497876)
I did a stupid simple thing for a system with a small fanout footprint. Not sure this scales.
The organizing principal was that if my code passed the acceptance tests once, the very same code should still pass with your service/library/data added to the mix. If they don’t, it’s likely your code and not mine.
This might not seem like much but it cuts hours of finger pointing out of a three party system. I expect this effect would be multiplied for a five or ten party scenario.
And in particular, latency has a huge negative impact on behavioral modification. People will keep doing things that they get yelled at over three weeks later. They will stop doing things they get called on hours later.
Which I would hope offsets the additional test matrix complexity.
The organizing principal was that if my code passed the acceptance tests once, the very same code should still pass with your service/library/data added to the mix. If they don’t, it’s likely your code and not mine.
This might not seem like much but it cuts hours of finger pointing out of a three party system. I expect this effect would be multiplied for a five or ten party scenario.
And in particular, latency has a huge negative impact on behavioral modification. People will keep doing things that they get yelled at over three weeks later. They will stop doing things they get called on hours later.
Which I would hope offsets the additional test matrix complexity.