Circuit Breaker Mission - WildFly Swarm

The Circuit Breaker pattern provides a generic mechanism for quickly and easily reporting whether or not a service is functioning properly. This allows a service to report information about a failure and decide whether to quickly fail or simply degrade gracefully instead of failing.

Modern cloud applications are often comprised of many smaller services which interact with each other in a many-to-many manner. Understanding when a service is failing or unavailable is critically important, which is the main reason for the Health Check pattern. In some cases though, you may want to provide an alternative response if a service interacts with a failing or unavailable service. For example, if service1 interacts with service2 and service2 begins to fail or become unavailable due to high load, simply detecting the failure and restarting service2 may not alleviate the issue. Instead, you may want to signal service1 to reduce the amount of load it puts on service2 until service2 returns to a normal state.

On this page you can invoke the greeting service. This service uses a name service. The invocations are protected by a circuit breaker. You can configure the state of the name service using the toggle button.

Greeting service

Results:

Name service

Requests: