Need advice about which tool to choose?Ask the StackShare community!

gRPC

1.1K
1.2K
+ 1
59
NSQ

135
327
+ 1
143
Add tool

gRPC vs NSQ: What are the differences?

gRPC: A high performance, open-source universal RPC framework. gRPC is a modern open source high performance RPC framework that can run in any environment. It can efficiently connect services in and across data centers with pluggable support for load balancing, tracing, health checking..; NSQ: A realtime distributed messaging platform. NSQ is a realtime distributed messaging platform designed to operate at scale, handling billions of messages per day. It promotes distributed and decentralized topologies without single points of failure, enabling fault tolerance and high availability coupled with a reliable message delivery guarantee. See features & guarantees.

gRPC can be classified as a tool in the "Remote Procedure Call (RPC)" category, while NSQ is grouped under "Message Queue".

Some of the features offered by gRPC are:

  • Simple service definition
  • Works across languages and platforms
  • Start quickly and scale

On the other hand, NSQ provides the following key features:

  • support distributed topologies with no SPOF
  • horizontally scalable (no brokers, seamlessly add more nodes to the cluster)
  • low-latency push based message delivery (performance)

gRPC and NSQ are both open source tools. It seems that gRPC with 22K GitHub stars and 5.12K forks on GitHub has more adoption than NSQ with 15.6K GitHub stars and 2.03K GitHub forks.

Slack, 9GAG, and Policygenius are some of the popular companies that use gRPC, whereas NSQ is used by Stripe, Docker, and Segment. gRPC has a broader approval, being mentioned in 53 company stacks & 48 developers stacks; compared to NSQ, which is listed in 21 company stacks and 8 developer stacks.

Advice on gRPC and NSQ
Pramod Nikam
Co Founder at Usability Designs | 2 upvotes 路 411.3K views
Needs advice
on
Apache ThriftApache ThriftKafkaKafka
and
NSQNSQ

I am looking into IoT World Solution where we have MQTT Broker. This MQTT Broker Sits in one of the Data Center. We are doing a lot of Alert and Alarm related processing on that Data, Currently, we are looking into Solution which can do distributed persistence of log/alert primarily on remote Disk.

Our primary need is to use lightweight where operational complexity and maintenance costs can be significantly reduced. We want to do it on-premise so we are not considering cloud solutions.

We looked into the following alternatives:

Apache Kafka - Great choice but operation and maintenance wise very complex. Rabbit MQ - High availability is the issue, Apache Pulsar - Operational Complexity. NATS - Absence of persistence. Akka Streams - Big learning curve and operational streams.

So we are looking into a lightweight library that can do distributed persistence preferably with publisher and subscriber model. Preferable on JVM stack.

See more
Replies (1)
Naresh Kancharla
Staff Engineer at Nutanix | 4 upvotes 路 408.7K views
Recommends
KafkaKafka

Kafka is best fit here. Below are the advantages with Kafka ACLs (Security), Schema (protobuf), Scale, Consumer driven and No single point of failure.

Operational complexity is manageable with open source monitoring tools.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of gRPC
Pros of NSQ
  • 25
    Higth performance
  • 14
    The future of API
  • 12
    Easy setup
  • 4
    Polyglot
  • 4
    Contract-based
  • 29
    It's in golang
  • 20
    Lightweight
  • 19
    Distributed
  • 18
    Easy setup
  • 16
    High throughput
  • 10
    Publish-Subscribe
  • 7
    Save data if no subscribers are found
  • 7
    Scalable
  • 6
    Open source
  • 5
    Temporarily kept on disk
  • 2
    Simple-to use
  • 1
    Load balanced
  • 1
    Free
  • 1
    Primarily in-memory
  • 1
    Topics and channels concept

Sign up to add or upvote prosMake informed product decisions

Cons of gRPC
Cons of NSQ
    Be the first to leave a con
    • 1
      Get NSQ behavior out of Kafka but not inverse
    • 1
      Long term persistence
    • 1
      HA

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    What is gRPC?

    gRPC is a modern open source high performance RPC framework that can run in any environment. It can efficiently connect services in and across data centers with pluggable support for load balancing, tracing, health checking...

    What is NSQ?

    NSQ is a realtime distributed messaging platform designed to operate at scale, handling billions of messages per day. It promotes distributed and decentralized topologies without single points of failure, enabling fault tolerance and high availability coupled with a reliable message delivery guarantee. See features & guarantees.

    Need advice about which tool to choose?Ask the StackShare community!

    Jobs that mention gRPC and NSQ as a desired skillset
    CBRE
    United States of America Texas Richardson
    CBRE
    United States of America Texas Richardson
    CBRE
    United States of America Texas Richardson
    CBRE
    United States of America Texas Richardson
    What companies use gRPC?
    What companies use NSQ?
    See which teams inside your own company are using gRPC or NSQ.
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with gRPC?
    What tools integrate with NSQ?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    What are some alternatives to gRPC and NSQ?
    GraphQL
    GraphQL is a data query language and runtime designed and used at Facebook to request and deliver data to mobile and web apps since 2012.
    RabbitMQ
    RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
    Kafka
    Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
    REST
    An architectural style for developing web services. A distributed system framework that uses Web protocols and technologies.
    MQTT
    It was designed as an extremely lightweight publish/subscribe messaging transport. It is useful for connections with remote locations where a small code footprint is required and/or network bandwidth is at a premium.
    See all alternatives