HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
twitter
finagle
Scala2011–2023
twitter / finagle

finagle

A fault tolerant, protocol-agnostic RPC system

Web DevelopmentData & DatabasesSystems & InfrastructureNetworking
Explore on GitHubRead Hacker News discussions
15Distinct people
17Mentions
0Explicit recommenders
8.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A fault tolerant, protocol-agnostic RPC system

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year17 dated mentions

Observed mentions: 2011-07-04 19:01:35 UTC to 2023-04-02 17:23:29 UTC.

02462011-01-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20112012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20112011-01-01 00:00:00 UTC2012-01-01 00:00:00 UTC202
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC615
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC303
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC000
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC202
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC303
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC110

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Finagle Status This project is used in production at Twitter (and many other organizations), and is being actively developed and maintained. Releases Releases are done on an approximately monthly schedule. While semver is not followed, the changelogs are detailed and include sections on public API breaks and changes in runtime behavior. Getting involved Website: https://twitter.github.io/finagle/ Source: https://github.com/twitter/finagle/ Mailing List: finaglers@googlegroups.com Chat: https://gitter.im/twitter/finagle Blog: https://finagle.github.io/blog/ 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: Foursquare ING Bank Pinterest SoundCloud Tumblr Twitter 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 We feel that a welcoming community is important and we ask that you follow Twitter's Open Source Code of Conduct in all interactions with the community. The release 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. License Copyright 2010 Twitter, Inc. Licensed under the Apache License, Version 2.0: https://www.apache.org/licenses/LICENSE-2.0
Read the full README on GitHub

What Hacker News says

17 sources
niftich·Oct 25, 2016
Some software that Twitter has put out: [1] Heron, a realtime, distributed, fault-tolerant stream processing engine - https://github.com/twitter/heron [2] Finagle, a fault tolerant, protocol-agnostic RPC system - https://github.com/twitter/finagle/ [3] FlockDB, a distributed, fault-tolerant graph database - https://github.com/twitter/flockdb [4] Gizzard, a flexible sharding framework for creating eventually-consistent distributed datastores - https://github.com/twitter/gizzard [5] Twemcache, a Twitter fork of Memcached - https://github.com/twitter/twemcache [6] Twemproxy, a fast, light-weight proxy for memcached and redis - https://github.com/twitter/twemproxy
In Twitter Plans Hundreds More Job Cuts as Soon as This Week
niftich·Jul 13, 2016
Twitter puts out a LOT of software, and open-sources a good portion. I don't know if this is smart in the sense of being overstaffed relative to their revenue, but they do it regardless. Some examples: [1] Fabric, an SDK for mobile apps - https://docs.fabric.io/android/fabric/overview.html [2] Heron, a realtime, distributed, fault-tolerant stream processing engine - https://github.com/twitter/heron [3] Finagle, a fault tolerant, protocol-agnostic RPC system - https://github.com/twitter/finagle/ [4] FlockDB, a distributed, fault-tolerant graph database - https://github.com/twitter/flockdb [5] Ruby implementation of the ICU (International Components for Unicode - https://github.com/twitter/twitter-cldr-rb [6] Clockwork Raven, Human-Powered Data Analysis with Mechanical Turk - https://github.com/twitter/clockworkraven [7] Gizzard, a flexible
Read the rest
sharding framework for creating eventually-consistent distributed datastores - https://github.com/twitter/gizzard [8] Twemcache, a Twitter fork of Memcached - https://github.com/twitter/twemcache [9] Twemproxy, a fast, light-weight proxy for memcached and redis - https://github.com/twitter/twemproxy [10] Iago, a webapp load tester - https://github.com/twitter/iago [11] Ospriet, a bestof/voting app - https://github.com/twitter/ospriet
In Vine isn’t growing and most of its top executives have left
bmdhacks·Feb 12, 2015
Take a look at the Stack class (an example of a free monad) and how it's used to compose clients: https://github.com/twitter/finagle/blob/master/finagle-core/... https://github.com/twitter/finagle/blob/master/finagle-core/... http://twitter.github.io/finagle/guide/Clients.html A client is a layer of various components like load balancers and stats recorders, but they're also all configurable. Only using the expressiveness of scala could such a data structure be created to compose all of these pieces, yet still keep them modifiable and type-safe.
In Go kit: Go in the modern enterprise
mariusaeriksen·Nov 23, 2012
Hello from the author. Indeed the vernacular has changed, and “systems programming” refers also to the distributed systems server software. Composable futures and promises are still fairly new in use; I would wager our systems are some of the largest using the techniques described therein. While this talk focused on composable IO and services, there is much more to it. Finagle (https://github.com/twitter/finagle) is where the rubber meets the road. Its interfaces are described in these terms and it makes great use of their power. Also, as with any talk, it is difficult to convey the message using only the slides.
In Systems Programming at Twitter
chrisdinn·Jun 8, 2012
Spray is a great library. It's full featured, with it's own Akka-based HTTP server and a full client lib. Smoke is a smaller, more focused tool. You will find a lot of things Spray does that Smoke does not. Smoke has a significantly different DSL, relying on Akka's composable Futures to take care of things like error handling. Smoke evolved through an attempt to build the simplest possible asynchronous HTTP services on top of Akka, without sacrificing any of the key features we needed to deploy those services at scale. The goal of Smoke is not so much to compete with Spray as it is to provide an HTTP-service-focused alternative to Finagle (https://github.com/twitter/finagle) that uses Akka Futures instead of Twitter Futures, and includes everything we needed to build, test and deploy those services quickly. So far, it's been working quite
Read the rest
well for us.
In Smoke: Simple, asynchronous scala HTTP powered by Akka

Showing the 15 most recent of 17 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.