42wim/fabio — explained in plain English
Analysis updated 2026-07-18 · repo last pushed 2018-02-04
Register a microservice in Consul and let Fabio route traffic to it automatically without touching a load balancer config.
Roll out a blue/green deployment by directing a portion of traffic to a new service version through Fabio.
Proxy raw TCP traffic for a database or other non-HTTP protocol through Fabio alongside your HTTP services.
Automatically stop sending traffic to an instance the moment Consul marks it unhealthy, without restarting Fabio.
| 42wim/fabio | 42wim/go-xmpp | aasheeshlikepanner/vase | |
|---|---|---|---|
| Stars | — | — | 0 |
| Language | Go | Go | Go |
| Last pushed | 2018-02-04 | 2020-01-24 | — |
| Maintenance | Dormant | Dormant | — |
| Setup difficulty | moderate | moderate | moderate |
| Complexity | 3/5 | 3/5 | 4/5 |
| Audience | ops devops | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires a running Consul cluster for service registration and health checks before Fabio can route anything.
Fabio is a load balancer that automatically routes traffic to your services without requiring manual configuration. Think of it as a smart traffic cop that directs incoming requests to the right destination based on rules you define through service registration, rather than a static config file you have to maintain and redeploy. The way it works is straightforward: your services register themselves with Consul (a service registry tool) along with health checks and routing rules. Fabio watches Consul, picks up those rules, and immediately starts directing traffic. If a service goes down, Consul marks it as unhealthy, and Fabio stops sending traffic to it. If you deploy a new instance, Fabio sees it and starts routing requests automatically. This happens without restarting Fabio itself. You'd use this if you're running a modern infrastructure where services come and go frequently, think cloud deployments, microservices, or any setup where instances scale up and down. Instead of manually updating a load balancer config every time you deploy or roll back, your infrastructure stays in sync automatically. Fabio handles both HTTP and HTTPS traffic, as well as raw TCP proxying for databases or other protocols. It also supports advanced features like directing some traffic to a new version of your service ("blue/green" deployments) to safely test changes. Major sites like Marktplaats in the Netherlands and Gumtree in Australia have been using it to handle thousands of requests per second in production. It's built in Go, a compiled language known for speed and low overhead, which means it runs efficiently without consuming much CPU or memory. The whole setup is designed to be simple: no complex configuration language, no special setup required, just register your service in Consul and let it go.
Fabio is a Go load balancer that watches Consul service registrations and automatically routes HTTP, HTTPS, and TCP traffic to healthy instances with no manual config edits.
Mainly Go. The stack also includes Go, Consul.
Dormant — no commits in 2+ years (last push 2018-02-04).
No license information was stated in the explanation.
Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.