twitter/finagle

Health v2 · maintenance only

Adoption not part of the score

8864 stars · 1431 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

Finagle is an extensible, fault-tolerant, protocol-agnostic RPC system for the JVM, written in Scala with idiomatic APIs for both Scala and Java. It provides uniform client and server APIs for protocols like HTTP/2, Thrift, MySQL, Redis, and Memcached, designed for high-concurrency distributed systems.

Use cases

• build fault-tolerant RPC services on the JVM
• implement high-concurrency servers in Scala or Java
• add distributed tracing with Zipkin to service calls
• write protocol-agnostic clients and servers for Thrift or HTTP
• build resilient microservice backends with load balancing and retries
• connect to MySQL, Redis, or Memcached with managed clients

When to choose

• you are building JVM-based distributed systems that need fault tolerance and load balancing
• you want uniform client/server APIs across multiple protocols
• you need battle-tested infrastructure proven at Twitter-scale production
• you want built-in Zipkin tracing and protocol extensibility

When to avoid

• your stack is not on the JVM
• you want a lightweight HTTP framework for simple web apps
• you prefer simpler, more modern RPC frameworks like gRPC with less Scala-specific complexity
• you need stable semantic versioning, since Finagle does not follow semver

Facets

library · maturity stable

rpc http-client http-server middleware tracing load-testing microservices backend networking developer-tools jvm fault-tolerance thrift http2 protocol-agnostic high-concurrency jvm linux macos

Member repositories

For agents

markdown · JSON · MCP: product_card(name="twitter/finagle")