A fault tolerant, protocol-agnostic RPC system
Scala Java Python Ruby Thrift Shell HTML
Pull request Compare This branch is 1 commit ahead, 555 commits behind twitter:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
bin
doc
finagle-benchmark-thrift/src/main/thrift
finagle-benchmark
finagle-cacheresolver
finagle-commons-stats
finagle-core
finagle-example
finagle-exception
finagle-exp
finagle-http-compat
finagle-http
finagle-kestrel
finagle-mdns
finagle-memcached
finagle-mux
finagle-mysql
finagle-native
finagle-netty4
finagle-ostrich4
finagle-redis
finagle-serversets
finagle-spdy
finagle-stats
finagle-stream
finagle-test
finagle-testers
finagle-thrift
finagle-thriftmux
finagle-validate
finagle-zipkin
project
site
.gitignore
.mailmap
.travis.yml
ADOPTERS.md
CHANGES
CONFIG.ini
CONTRIBUTING.md
CONTRIBUTORS
GROUPS
LICENSE
OWNERS
README.md
link-netty.sh
pushsite.bash
sbt

README.md

Finagle

Build status Coverage status Project status Gitter Maven Central

Status

This project is used in production at Twitter (and many other organizations), and is being actively developed and maintained.

Finagle logo

Getting involved

Finagle is an extensible RPC system for the JVM, used to construct high-concurrency servers. Finagle implements uniform client and server APIs for several protocols, and is designed for high performance and concurrency. Most of Finagle’s code is protocol agnostic, simplifying the implementation of new protocols.

For extensive documentation, please see the user guide and API documentation websites. Documentation improvements are always welcome, so please send patches our way.

Adopters

The following are a few of the companies that are using Finagle:

For a more complete list, please see our adopter page. If your organization is using Finagle, consider adding a link there and sending us a pull request!

Contributing

The master branch of this repository contains the latest stable release of Finagle, and weekly snapshots are published to the develop branch. In general pull requests should be submitted against develop. See CONTRIBUTING.md for more details about how to contribute.