Getting Started
Tripswitch is a remote circuit breaker. It evaluates dependency health centrally and lets your services enforce decisions locally.
Tripswitch gives you a shared decision signal, not a control loop.
What Tripswitch Is Not
Before going further, clear these out:
- Not a retry library. It won’t retry failed calls for you.
- Not an architectural wrapper. It may allow or block an attempt, but your service owns control flow and fallback behavior.
- Not automatic reliability. It provides information. You act on it.
SDKs exist to help you integrate cleanly, but execution and fallback logic remain yours.
Official SDKs: Go
The Shape of the Integration
At a high level, using Tripswitch looks like this:
- Create a project and define a breaker in the Tripswitch dashboard.
- Install the official Go SDK into your service.
- Check breaker state before calling a dependency.
- Report outcomes after execution.
That’s the loop. The SDK handles state synchronization and outcome batching. Your code handles execution and decision-making.
Before You Write Any Code
Read Integration Patterns first.
It explains where Tripswitch fits in your service, what the SDK does, what it does not do, and what responsibilities remain yours.
Do not skip this.
If you want to explore the Go SDK first, see the Go SDK repo.
Other Resources
Depending on where you are:
| If you need… | Go to |
|---|---|
| Background on circuit breakers | When Refusing to Run Is the Safer Choice |
| Understanding recovery behavior | Half-Open: The Critical Recovery Phase |
| Understanding evaluation logic | How Tripswitch Evaluates Health |
| Authentication setup | Authentication Guide |
| Breaker configuration reference | Breaker Kinds |
| API reference | API Documentation |
| SDKs | Go SDK on GitHub |
These are reference material. Integration Patterns is the next step if you’re integrating Tripswitch.