3 ms·
You seem to be missing the point though. Most developers working on microservices projects don't have to deal with the operational complexity. They just need to
by threeseed 10y ago
You seem to be missing the point though. Most developers working on microservices projects don't have to deal with the operational complexity. They just need to work on their microservice and don't have to know what is going on elsewhere.
Personally I much prefer microservices for debugging. You can quickly identify which one is the problem then test the APIs in isolation pretty quickly. Sure beats having to wait 20 minutes for a monolithic app to build.
- majormajor 10y agoSo what do these people do when they get data back from one of their dependency services, and it looks wrong? Or a bug is reported that somewhere in the chain, something is being dropped on the floor? You say you can quickly identify which one is the problem, but if that's a chain that spans 5 teams, how does that actually work in practice? (My experience is that it doesn't.) That's the sort of thing I was including in operational complexity, not just the "are the packets making it through" stuff.
- dahauns 10y agoExactly. Testing an API in isolation doesn't help you a thing when the bug arises because of, say, subtle inconsistencies between API implementations of interacting services on a long chain. This sounds a lot like the code coverage fallacy. (to which I usually answer "call me when you have 100% data coverage").