Great blog! ! I’ve dealt with circuit breaker pattern in the context of JaveScript, its cool to see it from the perspective of Go. I would recommend checking x-state if you’re interested its a NodeJS framework that handles state. Event-driven development for managing state machines is very powerful and might simplify the circuit breaker implementation, in other words becoming more reactive to change rather than constantly polling and checking thresholds. If you look up microservices choreography vs orchestration there are a couple of good blogs about implementing a reactive microservices architecture :)
Thanks! This is definitely an oversimplified example which I used for education, but re-building this pattern with an event-driven pattern sounds cool and interesting. I might write another article on that :)
Great blog! ! I’ve dealt with circuit breaker pattern in the context of JaveScript, its cool to see it from the perspective of Go. I would recommend checking x-state if you’re interested its a NodeJS framework that handles state. Event-driven development for managing state machines is very powerful and might simplify the circuit breaker implementation, in other words becoming more reactive to change rather than constantly polling and checking thresholds. If you look up microservices choreography vs orchestration there are a couple of good blogs about implementing a reactive microservices architecture :)
Thanks! This is definitely an oversimplified example which I used for education, but re-building this pattern with an event-driven pattern sounds cool and interesting. I might write another article on that :)
Cool! Looking forward for this demo :) Let me know if you want to collab on it I can pitch in with some ideas from the event-driven perspective!