Grizzly VS Netty

Grizzly

We haven't tracked posts mentioning Grizzly yet.
Tracking mentions began in Dec 2020.

Netty

• Reactor Netty: UDP DNS client example
  1 project | dev.to | 6 Apr 2024

  Code of netty is here and using following library

• Netty: Asynchronous event-driven network application framework
  1 project | news.ycombinator.com | 19 Mar 2024
• New scalable, fault-tolerant, and efficient open-source MQTT broker
  8 projects | news.ycombinator.com | 18 Dec 2023

  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
  4 projects | dev.to | 6 Dec 2023

  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
  1 project | news.ycombinator.com | 28 Aug 2023

  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
  2 projects | news.ycombinator.com | 14 Jul 2023

  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
  1 project | /r/eclipse | 22 Apr 2023

  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?
  1 project | /r/java | 14 Apr 2023

  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
  1 project | dev.to | 5 Apr 2023

  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.