avaje-jex
Netty
Our great sponsors
avaje-jex | Netty | |
---|---|---|
3 | 53 | |
19 | 32,765 | |
- | 0.9% | |
4.7 | 9.6 | |
6 months ago | 6 days ago | |
Java | 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.
avaje-jex
-
Libraries other than Spring Boot for creating web APIs
I created https://github.com/avaje/avaje-jex ... with the hope of helping to move Javalin more in the Java direction but yeah, Javalin isn't going in that direction. So avaje-jex now will follow it's own path (as pretty much a web routing layer that abstracts over various http servers like jetty, grizzly etc with a java and loom focus).
-
is anyone want to join maintaining spark java framework?
Well, ultimately I instead ended up creating jex - https://github.com/avaje/avaje-jex
-
Practical intro into creating Virtual Threads with project Loom
The Jetty ones use Jex and Loom based Jetty ThreadPool implementation ... and note that this isn't how the Jetty folks themselves have been playing around with Loom (see their loom branch). However, testing this just now against the latest 19 EA in what I think is the worst case scenario for Loom has: Loom at 80 rps and Traditional at 90 rps. Worse case scenario for loom meaning there is NO WAIT AT ALL in the response and that we do not exceed the Traditional Jetty thread pool size (testing at 100 concurrent clients which is less than default 200 max Jetty thread pool). As soon as we introduce IO wait + exceed the traditional thread pool size in terms of concurrent activity is when we see loom win out.
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?
test-driven-learning - Learning tests
Undertow - High performance non-blocking webserver
RESTEasy - An Implementation of the Jakarta RESTful Web Services Specification
OkHttp - Square’s meticulous HTTP client for the JVM, Android, and GraalVM.
Apache Spark - Apache Spark - A unified analytics engine for large-scale data processing
gRPC - The Java gRPC implementation. HTTP/2 based RPC
rest - Jakarta RESTful Web Services
Grizzly
manifold - Manifold is a Java compiler plugin, its features include Metaprogramming, Properties, Extension Methods, Operator Overloading, Templates, a Preprocessor, and more.
KryoNet - TCP/UDP client/server library for Java, based on Kryo
airlift - Airlift framework for building REST services
MINA - Mirror of Apache MINA