Udash
Finagle
| Udash | Finagle | |
|---|---|---|
| 1 | 24 | |
| 443 | 8,752 | |
| -0.2% | 0.1% | |
| 8.8 | 7.2 | |
| 7 days ago | 6 days ago | |
| Scala | Scala | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Udash
Finagle
-
Features of Project Loom incorporated in Java 21
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/webflu...
- Twitter Finagle: Backoff.scala
-
Twitter (re)Releases Recommendation Algorithm on GitHub
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/)
-
We switched from Scala 2 to Rust
So biased. Twitter dropping Scala3 is simply untrue, ticket is there and still is open https://github.com/twitter/finagle/issues/932
-
Introduction to Bazel for Scala developers
Thank you. I only took a quick look, but this looks like a goldmine of info if you are interested in using bazel to build a scala monorepo: https://github.com/twitter/finagle
-
Server Stack Options for Scala
Finagle
-
Elon: "[Twitter's] recommendation algorithm was using absolute block count, rather than percentile block count, causing accounts with many followers to be dumped, even if blocks were only 0.1% of followers."
And the engineering team are far from imbeciles because they built one of the worlds' best cache and RPC microservice components. As well as the fact that up until Musk took over the website was running just fine (other than your issue with product decisions).
-
Pretty incredible thread where Elon confuses how GraphQL works, thinks the Android client itself is making one thousand requests, and then publicly fires an employee who corrects him.
Bro it's their fucking project lolhttps://twitter.github.io/finagle/
-
Elon Musk publicly feuding with and firing his developers on Twitter
RPC generally means server side calls, probably this https://twitter.github.io/finagle/, and XHR is not RPC.
-
Pretending to know what you're talking about
not familiar with twitter internals but it would be atypical to use gql for internal communications even if you expose it as a public api. twitter also develops a widely-used RPC system https://github.com/twitter/finagle
What are some alternatives?
Laminar - Simple, expressive, and safe UI library for Scala.js
gRPC - The Java gRPC implementation. HTTP/2 based RPC
Binding.scala - Reactive data-binding for Scala
Netty - Netty project - an event-driven asynchronous network application framework
OutWatch - The Functional and Reactive Web-Frontend Library for Scala.js
OkHttp - Square’s meticulous HTTP client for the JVM, Android, and GraalVM.
Vert.x Web - The wiki and issues for the vert-x3 organisation
Akka - Build highly concurrent, distributed, and resilient message-driven applications on the JVM
Widok - Client-server skeleton
Finatra - Fast, testable, Scala services built on TwitterServer and Finagle
Korolev - Single Page Applications running on the server side.
Lagom - Reactive Microservices for the JVM