Scalability
Finagle is designed to work in highly concurrent environments and easily scales to handle thousands of requests per second, making it suitable for applications with high throughput requirements.
Protocol Agnostic
Finagle provides support for a wide range of protocols such as HTTP, Thrift, and more, allowing developers to integrate it with various network services without being tied to a specific protocol.
Asynchronous and Non-blocking
It uses asynchronous I/O and provides a non-blocking architecture that facilitates efficient resource utilization and improved application responsiveness.
Resilience Features
Includes built-in mechanisms for implementing retries, circuit breakers, and deadlines, enhancing the resilience of client-server communication.
Built-in Load Balancing
Comes with built-in load balancing that helps distribute requests evenly across service instances, thus improving application performance and reliability.
Extensible and Modular
Finagle's architecture is modular, allowing developers to extend or modify its functionality as needed by customizing different components.
We have collected here some useful links to help you find out if Finagle is good.
Check the traffic stats of Finagle on SimilarWeb. The key metrics to look for are: monthly visits, average visit duration, pages per visit, and traffic by country. Moreoever, check the traffic sources. For example "Direct" traffic is a good sign.
Check the "Domain Rating" of Finagle on Ahrefs. The domain rating is a measure of the strength of a website's backlink profile on a scale from 0 to 100. It shows the strength of Finagle's backlink profile compared to the other websites. In most cases a domain rating of 60+ is considered good and 70+ is considered very good.
Check the "Domain Authority" of Finagle on MOZ. A website's domain authority (DA) is a search engine ranking score that predicts how well a website will rank on search engine result pages (SERPs). It is based on a 100-point logarithmic scale, with higher scores corresponding to a greater likelihood of ranking. This is another useful metric to check if a website is good.
The latest comments about Finagle on Reddit. This can help you find out how popualr the product is and what people think about it.
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 / almost 3 years 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: over 3 years ago
Bro it's their fucking project lolhttps://twitter.github.io/finagle/. Source: over 3 years ago
You can even see it mentioned in Finagle's project, which is what Twitter uses https://twitter.github.io/finagle/. Source: over 3 years ago
RPC generally means server side calls, probably this https://twitter.github.io/finagle/, and XHR is not RPC. - Source: Hacker News / over 3 years 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 3 years 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 / almost 4 years 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 / almost 4 years 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: about 4 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 4 years ago
Finagle, possibly with Finch on top. Source: almost 5 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 / almost 5 years ago
Do you know an article comparing Finagle to other products?
Suggest a link to a post with product alternatives.
Is Finagle good? This is an informative page that will help you find out. Moreover, you can review and discuss Finagle 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.