Question 1

How to implement exponential backoff with gollback retry?

Accepted Answer

gollback's Retry function doesn't support backoff natively; you need to add sleep logic inside the callback, such as using time.Sleep with increasing durations, which can complicate error handling.

Question 2

gollback vs errgroup for concurrent tasks in Go

Accepted Answer

gollback focuses on race, all, and retry patterns with context support, while errgroup is better for synchronizing goroutines with error propagation. Choose gollback for simple retries or races, but errgroup for grouped task management.

Question 3

Can gollback handle panics in callbacks?

Accepted Answer

No, gollback does not catch or manage panics; if a callback panics, it will propagate and crash the program. You must add recovery logic within the callbacks themselves.

Question 4

How to cancel a specific callback in gollback All?

Accepted Answer

Cancellation is coarse-grained via context; gollback All waits for all callbacks to finish, and you cannot cancel individual ones. Use context cancellation to stop all operations if needed.

Question 5

Is gollback suitable for production use with high concurrency?

Accepted Answer

Yes, due to its performance-focused design and low allocations shown in benchmarks, but ensure error handling and type safety are managed, as it lacks built-in production features like metrics or logging.

Question 6

What happens if gollback Race gets no successful results?

Accepted Answer

Race returns the last error from the callbacks if all fail, as per the README description, so you should handle this error case in your code to avoid silent failures.

gollback

What is gollback?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions