Rick

Rick
Rick

Sunday, May 3, 2015

Circuit Breaker and Microservices Monitoring


Circuit Breaker and Microservices Monitoring
 
You can employ the Circuit Breaker pattern to prevent a catastrophic cascade, and reactive microservices monitoring can be the trigger. Downstream services can be registered in a service discovery so that you can mark nodes as unhealthy as well react by reroute in the case of outages. The reaction can be serving up a deprecated version of the data or service, but the key is to avoid cascading failure. You don't want your services falling over like dominoes.

Read more at Microservices Monitoring.
Kafka and Cassandra support, training for AWS EC2 Cassandra 3.0 Training