1. Usage
  2. How It Works
  3. Waiting
  4. Event Listeners
  5. Best Practices
  6. Standalone Usage

Bulkheads limit concurrent executions as a way of preventing system overload.


Creating and using a Bulkhead is simple:

// Permit 10 concurrent executions
bulkhead := bulkhead.With[any](10)
err := failsafe.Run(SendRequest, bulkhead)

How It Works

Executions are permitted in a bulkhead until it is full, meaning the max number of concurrent executions has been reached. Any further executions will either fail with ErrFull or will wait until permitted.


By default, when the max concurrent executions are exceeded, further executions will immediately fail with ErrFull. A bulkhead can also be configured to wait for execution permission if it can be achieved within a max wait time:

// Wait up to 1 second for execution permission
bulkhead := bulkhead.Builder[any](10).

Fairness is guaranteed with waiting executions, meaning they’re permitted in the order they’re received. Actual wait times for a bulkhead can vary depending on how busy it is. Since executions will block while waiting on a rate limiter, a maxWaitTime should be chosen carefully to avoid excessive blocking.

Event Listeners

A Bulkhead can notify you with an ExecutionEvent when the bulkhead is full:

builder.OnBulkheadFull(func(e failsafe.ExecutionEvent[any]) {
  logger.Error("Bulkhead full")

Best Practices

A Bulkhead can and should be shared across code that accesses finite resources. This ensures that if the bulkhead is full, all executions that access the same resource and use the same bulkhead will either wait or fail until executions are permitted again. For example, if multiple connections or requests are made to the same external server, you may route them through the same bulkhead.

Standalone Usage

A Bulkhead can also be manually operated in a standalone way:

if bulkhead.TryAcquirePermit() {