I have just started with Nameko. I am amazed by the simplicity of the Nameko framework and how it is so easy to develop services with this.
I tried with one sample service and integerated it with Flask using flask_nameko. Everything is working fine but i’m confused with one thing. It may sound silly but rpc and nameko is pretty new to me, so the thing is my worker/service got crashed suddenly, now when i try to hit the API, it just publishes the event in the queue and waits for the result while on the side, the worker is down; so it stucks permanently there.
Though i know about the circuit breaking concept in http based microservice where if one service is down, circuit breaks and we can return a default/custom response. So, can someone tell me how does circuit breaking thing can be apllied in the case of rpc based microservice.
My apologies if this is a stupid question, but i’m stuck with my development here on this thing. Kindly help me with some references.