facebook/wangle

Wangle is a framework providing a set of common client/server abstractions for building services in a consistent, modular, and composable way.

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 14 minutes ago
Added to GitGenius on September 22nd, 2026
Created on December 11th, 2014
Open Issues & Pull Requests: 48 (+0)
GitHub issues: Enabled
Number of forks: 547
Total Stargazers: 3,092 (+0)
Total Subscribers: 158 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.1 hours
Mean response time: 90.6 days
90th percentile: 181.2 days
Tracked items: 2

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 768 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Wangle is a C++ framework that provides client and server abstractions for building services in a consistent, modular, and composable way.

Wangle solves the problem of writing networked services by offering high-level abstractions built on top of folly's asynchronous I/O primitives. It combines two layers of abstraction: a client/server layer with ServerBootstrap and ClientBootstrap for managing thread pools and connection pipelines, and a request/response layer inspired by Finagle that handles protocol-agnostic concerns like load balancing, connection pooling, and retry logic. Developers define pipelines of handlers that process socket data, and services that implement matched client/server interfaces. Filters can be applied at both the service level (for request-level concerns like timeouts and rate limiting) and the factory level (for connection-level concerns like pooling and load balancing).

Wangle suits teams building services in C++ who want the kind of structured, composable abstractions available in languages like Java and Python. It works well for any request/response protocol, including Thrift and HTTP. The framework requires folly, fizz, CMake, and OpenSSL as dependencies. A tutorial and examples are provided to help developers get started, including a basic echo server and client implementation.

The project maintains a steady stream of commits across its codebase with consistent activity in core modules. Pull requests receive timely review and integration. The issue tracker shows regular engagement with bug reports and feature discussions. Development spans multiple areas including pipeline handling, service abstractions, and protocol-specific implementations, indicating active maintenance of the framework's breadth.