Based on our record, Finagle should be more popular than NSQ. It has been mentiond 12 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
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/webflux/reactive-spring.html. - Source: Hacker News / 9 months ago
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/). Source: about 1 year ago
Bro it's their fucking project lolhttps://twitter.github.io/finagle/. Source: over 1 year ago
You can even see it mentioned in Finagle's project, which is what Twitter uses https://twitter.github.io/finagle/. Source: over 1 year ago
RPC generally means server side calls, probably this https://twitter.github.io/finagle/, and XHR is not RPC. - Source: Hacker News / over 1 year ago
(G)NATS can do millions of messages per second and is the right tool for the job (either that or NSQ). Redis isn't even the fastest Redis protocol implementation, KeyDB significantly outperforms it. Source: about 1 year ago
Bit.ly's NSQ is also an excellent message queue option. Source: about 1 year ago
Queue consumers are interesting because there are many solutions for them, from using Redis and persisting the data in a data store - but for fast and scalable the approach I would take is something like SQS (as I advocate AWS even free tier) or NSQ for managing your own distributed producers and consumers. Source: over 1 year ago
Distrubition server engine ( for example websocket server multi ws gateway and worker pool,nsq.io realtime message queue and so on). Source: almost 2 years ago
NSQ is a message queue implemented by Golang, and all messages are routed through NSQ. Reasons for choosing NSQ compared to other MQs: decentralized distribution (direct connection between production and consumption), low latency, No ordering, high performance, simple binary protocol. - Source: dev.to / about 2 years ago
Akka - Build powerful reactive, concurrent, and distributed applications in Java and Scala
ZeroMQ - ZeroMQ is a high-performance asynchronous messaging library.
RxJS - Reactive Extensions for Javascript
RabbitMQ - RabbitMQ is an open source message broker software.
Netty - Cloud-based real estate management solution
nanomsg - nanomsg is a socket library that provides several common communication patterns.