Not sure about now but a few years back the company I worked for was heavily vested in Finagle [1] using Future pools. I'm sure virtual threads would only enhance this framework. Also, Spring and it's reactive webflux would probably benefit as well [2]. [1] https://twitter.github.io/finagle/ [2] https://docs.spring.io/spring-framework/reference/web/webflux/reactive-spring.html. - Source: Hacker News / 9 months ago
Don't really see how "enterprise scala" has anything to do with this, scala is meant to be parallelized , that's like it's whole thing with akka / actors / twitter's finagle (https://twitter.github.io/finagle/). Source: about 1 year ago
Bro it's their fucking project lolhttps://twitter.github.io/finagle/. Source: over 1 year ago
You can even see it mentioned in Finagle's project, which is what Twitter uses https://twitter.github.io/finagle/. Source: over 1 year ago
RPC generally means server side calls, probably this https://twitter.github.io/finagle/, and XHR is not RPC. - Source: Hacker News / over 1 year ago
Twitter is a Scala shop and specifically uses Finagle - a homegrown RPC framework based on Apache Thrift. Https://twitter.github.io/finagle/. Source: over 1 year ago
When breaking up a monolithic app into microservices, the communication between these services becomes vital to the health and performance of the application. Technically, you could incorporate the features to manage this traffic directly into your application. This is what Twitter, Google, and Netflix did with massive internal libraries like Finagle, Stubby, and Hysterix. - Source: dev.to / over 1 year ago
I think the more interesting aspect of this is the framework being used: https://github.com/micro/micro I haven't dug into it at all yet, but at a glance it looks like it's aiming to do something similar to what Go kit (https://gokit.io/) or Finagle (https://twitter.github.io/finagle/) does, where it gives you a nice abstraction for defining your "service" and then handles all the supplementary aspects (service... - Source: Hacker News / over 1 year ago
I’m a software engineer. Twitter’s original code was REALLY good - they open sourced some of it back in the day). They still need tech talent to keep it site running smoothly. Source: almost 2 years ago
This comes dangerously close to functional services as popularized by Twitter et al and encapsulated in the well known Finagle library. I don’t know but I strongly suspect /u/peterbourgon was heavily influenced by this while developing the notion of Endpoints in his reasonably well known go-kit library, although it’s significantly less general due mostly to limitations in Go’s type system. Source: over 2 years ago
Finagle, possibly with Finch on top. Source: over 2 years ago
OK, so let's say you follow this approach. Twitter did precisely this with their Finagle RPC system. Functionality like request metrics, traffic splitting, retries, and more was coded once and then shared across every service at Twitter. Well, that is, every service at Twitter that runs on the JVM. - Source: dev.to / over 2 years ago
Do you know an article comparing Finagle to other products?
Suggest a link to a post with product alternatives.
This is an informative page about Finagle. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.