3 ms·
You should not need to do this with microservices. Part of creating them is implementing well-defined API's, which create concrete borders between your service
by qyv 9y ago
You should not need to do this with microservices. Part of creating them is implementing well-defined API's, which create concrete borders between your services. It is extremely easy to capture/log all traffic passing between your services, which you should be able to use to determine which service is misbehaving, and them aim your debugger there. If you cannot do this, then your API's are not doing what they are supposed to be doing.
- joshribakoff 9y ago> It is extremely easy to capture/log all traffic passing between your services But you would have to create a development environment running the complete micro-services environment on a single machine. Or setup distributed/cloud logging & debug against production. Which is generally easier to do if you use a monolith. Admittedly tools like docker compose and vagrant can help with this.