avaje-jex
Netty
Our great sponsors
avaje-jex | Netty | |
---|---|---|
3 | 52 | |
19 | 32,626 | |
- | 0.8% | |
4.7 | 9.5 | |
5 months ago | 4 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
-
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.
-
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
- Gradle 8.0
-
[ANN] Retty v0.6.0 - An asynchronous Rust networking framework that makes it easy to build protocols, application clients/servers.
It's like Netty or Wangle, but in Rust.
-
Unity MVVM
DotNetty is a port of Netty, asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.
-
Possibly stupid question, is java the right language for low latency and high throughput web servers?
As you are in i/o tasks, you can look at spring webflux / microprofile / quarkus. If you mature enough netty (https://netty.io/) based solution will be more effecient.
-
[ANN] Retty v0.3.0 - An asynchronous Rust networking framework that makes it easy to build protocols, application clients/servers.
It's like Netty or Wangle, but in Rust.
-
ShardingSphere-Proxy Front-End Protocol Troubleshooting Guide and Examples
In the ShardingSphere-Proxy front-end Netty decoding logic, when a data Packet of length 0xFFFFFF is encountered, the Payload part of multiple MySQL Packets is aggregated via CompositeByteBuf.
What are some alternatives?
Undertow - High performance non-blocking webserver
OkHttp - Square’s meticulous HTTP client for the JVM, Android, and GraalVM.
gRPC - The Java gRPC implementation. HTTP/2 based RPC
Grizzly
KryoNet - TCP/UDP client/server library for Java, based on Kryo
MINA - Mirror of Apache MINA
Async Http Client - Asynchronous Http and WebSocket Client library for Java
Dubbo - The java implementation of Apache Dubbo. An RPC and microservice framework.
Apache Tomcat - Apache Tomcat
Finagle - A fault tolerant, protocol-agnostic RPC system
message-io - Fast and easy-to-use event-driven network library.
sshj - ssh, scp and sftp for java