Repository navigation
Is Finagle still maintained? #943
Description
Hi folks 👋 is this project still maintained? I see some housekeeping commits, but will you be actively developing new features?
Reacted by Hartmut Pfarr, Paul Friedrich Schulz, cedricsap, Peter Fröhlich, gutefrage.net IT, peter-janssen, Mikael Fridh and Márcio P. Dantas
Activity
xin301x commentedon Feb 23, 2023
felixbr commentedon Sep 21, 2023
I think the answer at this point is no, at least not publicly on github.
The bigger question is if we should try to fork and maintain the open-source version of Finagle separately going forward. By "we" I mean companies and people that still use Finagle for production deployments and have no immediate interest in replacing it with a different solution anytime soon.
Finagle is still a very robust framework and I haven't seen many alternatives that have the same features or reliability.
I would offer some of my time to keep basic maintenance up (like Scala versions, newer JDK versions, security updates). But I cannot do everything alone as this is a big project and a bus factor of 1 is always bad. My hope would be that devs from other companies which use Finagle will share the responsibility in a collaboration effort.
I'm tagging some people I've had the pleasure to collaborate with on Finagle and related projects in the past who might also still use Finagle and have some thoughts on this: @martijnhoekstra @pjfanning @bpholt @dangerousben
Cheers
pjfanning commentedon Sep 21, 2023
After spending nearly a year on Apache Pekko - a fork of Akka (due Akka's license change) - I'm not super anxious to get involved in another large fork.
If a Finagle fork is done, would you expect to soon have to fork other Twitter repos like the twitter/util project?
If X/Twitter were amenable and a small community could be formed, it may be feasible to get the code granted to the ASF and a new Incubator podling formed. I am a member of the Apache Incubator PMC and could help with this transfer. In the absence of X/Twitter granting the code to the ASF, it would be difficult to proceed on the ASF route. It would possibly be easier for someone to just fork FInagle themselves and try making a few releases under their own Maven groupId.
felixbr commentedon Sep 22, 2023
@pjfanning A fork would include twitter/util (as that's the basis for finagle), twitter/finagle, and possibly twitter-server. Of course, I wouldn't expect someone to maintain things they don't use themselves.
I don't think X/Twitter will help in any way, as they haven't even communicated their departure from open-source nor updated the "Status" in readme files. So I expect a fork to be made without their approval or help under a new groupId.
dangerousben commentedon Sep 22, 2023
I'm afraid I'll have to regretfully decline: I'm not currently using scala at work and don't have the free time for a side project of this nature.
FWIW, although I'm a bit out of the loop, if I were to start a large scala server project today I'd probably start by looking at the typelevel stack. It's nowhere near as 'batteries included' as finagle, but I believe there are enough third-party additions to bring it up to feature parity. I couldn't comment on performance, but then who can?
I realise this is no help whatsoever to those maintaining large existing finagle codebases. Hopefully there are enough people in that position to at least continue basic maintenance.
felixbr commentedon Sep 26, 2023
@dangerousben That's perfectly fine. I'm just asking to see who else is using Finagle in a similar situation. If you don't even use Scala currently then this isn't your concern at all and I apologize for tagging you.
Your assertion of the typelevel stack is spot on and we're already using it heavily in many projects (with and without Finagle).
bpholt commentedon Sep 26, 2023
I should be able to help with this kind of basic maintenance, at least for a while, but I can't spend a ton of time on it. My company uses Thrift Finagle, but we've been moving to the Typelevel stack for new applications, and this has sparked conversations about accelerating the transition for existing apps as well.
I'm hoping I'll get some time to work on Scalafix rules or other techniques to make that migration easier. We have the advantage that we never adopted the changes the Scrooge team made to remove the effect parameter in the generated interfaces—in fact, I wrote Scalafix rules to re-introduce the higher kinded type parameter into the generated traits that extend
ThriftService.Actually, that reminds me that IMO twitter/scrooge should also be included in the list of repos to fork.
DieBauer commentedon Nov 1, 2023
I see more movement here and at twitter/util. @mattdickinson5 do you know what the plans are with open-source Finagle and Util? Can we expect a release, or multiple in the future?
martijnhoekstra commentedon Nov 1, 2023
My company doesn't use any of the twitter stack, my main interest in keeping up updated before was more of a testbed for scala releases themselves, because it exercises a large part of the stack. If you need any concrete help with anything, I'm happy to take a look, but won't have capacity to coordinate anything.
csaltos commentedon Mar 19, 2024
Meanwhile at Twitter, the development department released version "23.11.0" and they are scheduling to launch version "24.2.0" soon.
Certainly Twitter is not releasing versions at a fast an massive rate as before but Finagle is not dead ... Scala and Finagle are the main backbone of Twitter for the backend and they have to keep it alive even at a slow pace.
Additionally Finagle is a mature product, it has a lot of features already a lot of hours of work and it's really good, we use it at my company and is very very fast and performant and more over that you can reason about it ... so to be pragmatic, Finagle at this point does not require a crazy development with releases every week, it's a pity Elon Musk decided to cut resources at Twitter but, again, Finagle has to be kept alive for Twitter be alive.
niodice commentedon Mar 21, 2024
@csaltos, is this information stated publicly anywhere?
marciopd commentedon Apr 23, 2025
Hey, guys. Any updates on this?
csaltos commentedon Apr 28, 2025
It's open source, you can fork it anytime, just mention the owners in the new license and you are good to go.
Maintaining a big piece of software like Finagle is very demanding, so it would be great to do it as a team starting with a proposal to the Apache Software foundation to accept the new fork under the wing of Apache Software foundation, like Akka into Pekko by instance.
Then as a team we can all collaborate and make an even better new piece of software based on Finagle using Apache resources and huge help.
dangerousben commentedon Apr 28, 2025
csaltos commentedon Apr 28, 2025
Remove finch
rbscgh commentedon Nov 21, 2025
fwiw there does seem to be some small pushes to util https://github.com/twitter/util/commits/f8735d20dc18acb728fe89bf0373a744e46ae67d/
csaltos commentedon Nov 21, 2025
Thank you very much for revivebird ... it's so valuable and important.
I have one question, the Finagle name can be kept? ... when you fork an open source project you need to give attribution, of course, but also you need to legally change the name to the project to something else ... think of these open source forks:
XFree86 -> X.Org Server
OpenOffice -> LibreOffice
KDE -> TDE
Java -> OpenJDK
Full disclosure, I'm not a lawyer, maybe worth make a professional research beacause all of them changed for legal considerations, trade marks and governance
A new name for the fork could be GoldFeather