bfenetworks/bfe

A modern layer 7 load balancer from baidu

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 40 minutes ago
Added to GitGenius on September 10th, 2026
Created on July 31st, 2019
Open Issues & Pull Requests: 33 (+0)
GitHub issues: Enabled
Number of forks: 949
Total Stargazers: 6,260 (+0)
Total Subscribers: 198 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

BFE is a layer 7 load balancer written in Go that handles HTTP and HTTPS traffic routing and distribution.

The tool addresses the need for efficient request distribution across backend servers at the application layer. It operates as a reverse proxy, accepting incoming connections and forwarding them to appropriate backend services based on routing rules. BFE implements standard load balancing capabilities including session persistence, health checking, and traffic shaping to manage how requests flow through your infrastructure.

BFE suits organizations running microservices or distributed systems that need sophisticated request routing beyond simple round-robin distribution. It works well for teams already invested in Go-based infrastructure or those operating in cloud-native environments. The project is particularly relevant for deployments where layer 7 visibility and control matter—scenarios involving content-based routing, header manipulation, or request filtering. Teams should evaluate whether they need the specific feature set BFE provides rather than adopting it as a generic replacement for any load balancer; the README does not position it against other tools in the category.

Development on the project shows consistent activity with regular commits across the codebase. The maintainers respond to issues and pull requests, indicating active stewardship of the repository. The project maintains documentation and examples that support users in getting started and understanding configuration options. Code changes suggest ongoing refinement of existing functionality rather than rapid feature expansion, reflecting a focus on stability and reliability in the core load balancing path.