Finagle
Netty
Our great sponsors
Finagle | Netty | |
---|---|---|
24 | 53 | |
8,753 | 32,765 | |
0.2% | 0.9% | |
7.1 | 9.6 | |
27 days ago | 2 days ago | |
Scala | Java | |
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.
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
Netty
-
Reactor Netty: UDP DNS client example
Code of netty is here and using following library
- Netty: Asynchronous event-driven network application framework
-
New scalable, fault-tolerant, and efficient open-source MQTT broker
We use Netty (https://netty.io/) as the source of the MQTT communication, and we build the MQTT features the MQTT broker should support ourselves on top of that.
-
Modern Async Primitives on iOS, Android, and the Web
In this space, we also have the somewhat related term blocking. Java's NIO library is one well-known non-blocking tool used for managing multiple tasks on a single Java thread. When listening to sockets, most of the time a thread is just blocked, doing nothing until it receives some data. So, it's efficient to use a single thread for monitoring many sockets, to increase the likelihood of the thread having some actual work to do. The Selector API does this but is notoriously challenging to program well. Instead, developers use frameworks like Netty which abstract some of NIO's complexity and layer on some best practices.
-
An investigative journey through concurrent data structures
DirectByteBuffer exhibits an intriguing behavior: it deallocates its backing memory during the finalization process, which occurs after garbage collection (GC) cycles. This poses an issue if your system is conservative with on-heap allocations, leading to infrequent GC cycles. In such cases, there could be a significant delay between the time the memory becomes unreferenced and when it is actually deallocated. This behavior could, in some respects, mimic a memory leak.
This is why some libraries hacks into DirectByteBuffer to deallocate memory explicitly, bypassing the finalizer altogether. For instance, the Netty library has implemented such a workaround, see Netty as an [example](https://github.com/netty/netty/blob/795db4a866401aa172757b95...).
-
Scaling to ~15K requests per second with Java – Part 1
Apologies replying to myself, but Netty, which underpins many of the popular Java backend frameworks, see backward compatibility as more important than supporting green threads.
https://github.com/netty/netty/issues/12816
It'll be interesting to see who (if anyone) picks up Netty's mantle in the Project Loom world.
-
Netty VS java-http - a user suggested alternative
2 projects | 25 May 2023
-
Is jre17 the problem? How do I get an old eclipse? Error: Could not find or load main class netty.DiscardServer Caused by: java.lang.ClassNotFoundException: netty.DiscardServer
Looks fairly recent so I'm glad I had a pre oct22 build https://github.com/netty/netty/issues/12737
-
What are your (favourite) Java best practices, personal tips, hints or just underrated stuff in general?
This is better? https://github.com/netty/netty/blob/4.1/pom.xml
-
Lessons learned from picking a Java driver for Amazon ElastiCache for Redis - Part 2
Given the fact that Lettuce is built with Netty, we also immediately noticed quite an impact on the initialization time (cold start) of our lambda function. Netty is really fast while executing, but takes a bit of time to initialize. The new Lambda Snapstart functionality might help with that.
What are some alternatives?
gRPC - The Java gRPC implementation. HTTP/2 based RPC
Undertow - High performance non-blocking webserver
OkHttp - Square’s meticulous HTTP client for the JVM, Android, and GraalVM.
Akka - Build highly concurrent, distributed, and resilient message-driven applications on the JVM
Finatra - Fast, testable, Scala services built on TwitterServer and Finagle
Grizzly
Lagom - Reactive Microservices for the JVM
KryoNet - TCP/UDP client/server library for Java, based on Kryo
Dubbo - The java implementation of Apache Dubbo. An RPC and microservice framework.
MINA - Mirror of Apache MINA