You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* refactor: improve error handling and logging in OutboxDispatcher
* feat: add CircuitBreakerSettings configuration options
* feat: implement Circuit Breaker pattern for database operation resilience
* feat: enhance Circuit Breaker with logging and configuration updates
* test: update tests to assert no exceptions are thrown during event processing
* refactor: improve documentation and clarity in MissingEventsCoordinator
* chore: update CHANGELOG for v1.5.0 release with new Circuit Breaker features and enhancements
* refactor: update Outbox event keys in configuration for consistency
Copy file name to clipboardExpand all lines: README.md
+14-1Lines changed: 14 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -106,6 +106,15 @@ value).
106
106
> If there will be multiple instances, the `MasterPodSettings.IsActive` should be set to `true`. Otherwise, messages can
107
107
> be duplicated or not published.
108
108
109
+
### Circuit Breaker
110
+
111
+
The application uses circuit breakers to handle database operation failures gracefully. Each daemon (OutboxEventsDaemon and MissingEventsDaemon) has its own circuit breaker that:
112
+
113
+
1. Opens after `Threshold` consecutive database failures (default: 3)
114
+
2. Stays open for `DurationMs` (default: 30 seconds)
115
+
3. Allows `HalfOpenMaxAttempts` (default: 1) operations when half-open
116
+
4. Automatically closes if operations succeed in half-open state
117
+
109
118
## Configuration
110
119
111
120
The application can be configured using the `config.json` and `secret.json` files. Here are the configurations you can
0 commit comments