Is there an existing issue that is already proposing this?
[X] I have searched the existing issues
Is your feature request related to a problem? Please describe it
In a microservice architecture where multiple microservices call each other and the API gateway handles the final invocation, exception handling can often be challenging. Although there are established methods, they may not always perform as expected and can frequently cause issues. Is there a better pattern? Can we supplement this with examples or documentation?
Describe the solution you'd like
There are too few examples of cooperation between multiple microservices, and there is a lack of corresponding documents.
Do you have any suggestions on what we could improve specifically? Not sure if that's something that fits in the document or should rather be its own article
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
In a microservice architecture where multiple microservices call each other and the API gateway handles the final invocation, exception handling can often be challenging. Although there are established methods, they may not always perform as expected and can frequently cause issues. Is there a better pattern? Can we supplement this with examples or documentation?
Describe the solution you'd like
There are too few examples of cooperation between multiple microservices, and there is a lack of corresponding documents.
Teachability, documentation, adoption, migration strategy
Not
What is the motivation / use case for changing the behavior?
When multiple microservices call each other, filters are too abstract and always not easy to control.