NSQ VS Faye

Compare NSQ VS Faye and see what are their differences

Cyclr

Powerful SaaS integration toolkit for SaaS developers - create, amplify, manage and publish native integrations from within your app with Cyclr's flexible Embedded iPaaS. featured

Contents:

» Base Details
» Videos
» Reviews
» Alternatives

NSQ

A realtime distributed messaging platform.

Faye

Simple pub/sub messaging for the web

Landing page //
2023-07-07

Landing page //
2021-10-17

GopherCon 2014 Spray Some NSQ On It by Matt Reiferson

Faye videos

+ Add

Chloé Faye: Review & What's In My Bag | The Anna Edit

Category Popularity

0-100% (relative to NSQ and Faye)

Faye

Stream Processing

100 100%

Stream Processing

0% 0

Developer Tools

0 0%

Developer Tools

100% 100

Data Integration

77 77%

Data Integration

23% 23

App Development

0 0%

App Development

100% 100

User comments

Share your experience with using NSQ and Faye. For example, how are they different and which one is better?

Reviews

These are some of the external sources and on-site user reviews we've used to compare NSQ and Faye

NSQ Reviews

NATS vs RabbitMQ vs NSQ vs Kafka | Gcore

NSQ is designed with a distributed architecture around the concept of topics, which allows messages to be organized and distributed across the cluster. To ensure reliable delivery, NSQ replicates each message across multiple nodes within the NSQ cluster. This means that if a node fails or there’s a disruption in the network, the message can still be delivered to its intended...

Source: gcore.com

Faye Reviews

We have no reviews of Faye yet.
Be the first one to post

Social recommendations and mentions

Based on our record, NSQ should be more popular than Faye. It has been mentiond 7 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.

NSQ mentions (7)

Any thoughts on using Redis to extend Go's channels across application / machine boundaries?
(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
FileWave: Why we moved from ZeroMQ to NATS
Bit.ly's NSQ is also an excellent message queue option. Source: about 1 year ago
Infinite loop pattern to poll for a queue in a REST server app
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
What are pros and cons of Go?
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
Distributed IM Service in Golang
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

Faye mentions (2)

8 Best WebSocket Libraries For Node
Faye WebSocket is a versatile WebSocket implementation derived from the Faye project. Faye is a messaging system that uses the Publish/Subscribe model and the Bayeux protocol. It provides message servers for Node, Ruby, and all major web browsers. - Source: dev.to / 7 months ago
Which self hosted Pub/Sub realtime technology (websockets etc) do you use and why?
I can find socket.io, faye, deepstream.io , autobahn-js and nchan, centrifugo. Can you also explain why you chose it and if you had troubles with some other solution? Source: about 3 years ago