Apache Flink vs NSQ

Overview

NSQ

Stacks142

Followers356

Votes148

Apache Flink

Stacks534

Followers879

Votes38

GitHub Stars25.4K

Forks13.7K

Apache Flink vs NSQ: What are the differences?

Apache Flink: Fast and reliable large-scale data processing engine. Apache Flink is an open source system for fast and versatile data analytics in clusters. Flink supports batch and streaming analytics, in one system. Analytical programs can be written in concise and elegant APIs in Java and Scala; 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.

Apache Flink and NSQ are primarily classified as "Big Data" and "Message Queue" tools respectively.

Some of the features offered by Apache Flink are:

Hybrid batch/streaming runtime that supports batch processing and data streaming programs.
Custom memory management to guarantee efficient, adaptive, and highly robust switching between in-memory and data processing out-of-core algorithms.
Flexible and expressive windowing semantics for data stream programs

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)

"Unified batch and stream processing" is the primary reason why developers consider Apache Flink over the competitors, whereas "It's in golang" was stated as the key factor in picking NSQ.

Apache Flink and NSQ are both open source tools. NSQ with 15.6K GitHub stars and 2.03K forks on GitHub appears to be more popular than Apache Flink with 9.35K GitHub stars and 5K GitHub forks.

According to the StackShare community, Apache Flink has a broader approval, being mentioned in 20 company stacks & 22 developers stacks; compared to NSQ, which is listed in 21 company stacks and 8 developer stacks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on NSQ, Apache Flink

Nilesh

Technical Architect at Self Employed

Jul 8, 2020

Needs adviceon

Elasticsearch

Kafka

We have a Kafka topic having events of type A and type B. We need to perform an inner join on both type of events using some common field (primary-key). The joined events to be inserted in Elasticsearch.

In usual cases, type A and type B events (with same key) observed to be close upto 15 minutes. But in some cases they may be far from each other, lets say 6 hours. Sometimes event of either of the types never come.

In all cases, we should be able to find joined events instantly after they are joined and not-joined events within 15 minutes.

576k views576k

Comments

Pramod

Co Founder at Usability Designs

Mar 2, 2020

Needs advice

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.

572k views572k

Comments

Detailed Comparison

NSQ	Apache Flink
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.	Apache Flink is an open source system for fast and versatile data analytics in clusters. Flink supports batch and streaming analytics, in one system. Analytical programs can be written in concise and elegant APIs in Java and Scala.
support distributed topologies with no SPOF;horizontally scalable (no brokers, seamlessly add more nodes to the cluster);low-latency push based message delivery (performance);combination load-balanced and multicast style message routing;excel at both streaming (high-throughput) and job oriented (low-throughput) workloads;primarily in-memory (beyond a high-water mark messages are transparently kept on disk);runtime discovery service for consumers to find producers (nsqlookupd);transport layer security (TLS);data format agnostic;few dependencies (easy to deploy) and a sane, bounded, default configuration;simple TCP protocol supporting client libraries in any language;HTTP interface for stats, admin actions, and producers (no client library needed to publish);integrates with statsd for realtime instrumentation;robust cluster administration interface (nsqadmin)	Hybrid batch/streaming runtime that supports batch processing and data streaming programs.;Custom memory management to guarantee efficient, adaptive, and highly robust switching between in-memory and data processing out-of-core algorithms.;Flexible and expressive windowing semantics for data stream programs;Built-in program optimizer that chooses the proper runtime operations for each program;Custom type analysis and serialization stack for high performance
Statistics
GitHub Stars -	GitHub Stars 25.4K
GitHub Forks -	GitHub Forks 13.7K
Stacks 142	Stacks 534
Followers 356	Followers 879
Votes 148	Votes 38
Pros & Cons
Pros 29 It's in golang 20 Lightweight 20 Distributed 18 Easy setup 17 High throughput Cons 1 HA 1 Long term persistence 1 Get NSQ behavior out of Kafka but not inverse	Pros 16 Unified batch and stream processing 8 Easy to use streaming apis 8 Out-of-the box connector to kinesis,s3,hdfs 4 Open Source 2 Low latency
Integrations
No integrations available	YARN Hadoop Hadoop HBase Kafka

What are some alternatives to NSQ, Apache Flink?

Kafka

Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.

RabbitMQ

RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.

Celery

Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.

Amazon SQS

Transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. With SQS, you can offload the administrative burden of operating and scaling a highly available messaging cluster, while paying a low price for only what you use.

Apache Spark

Spark is a fast and general processing engine compatible with Hadoop data. It can run in Hadoop clusters through YARN or Spark's standalone mode, and it can process data in HDFS, HBase, Cassandra, Hive, and any Hadoop InputFormat. It is designed to perform both batch processing (similar to MapReduce) and new workloads like streaming, interactive queries, and machine learning.

ActiveMQ

Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License.

ZeroMQ

The 0MQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialised messaging middleware products. 0MQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more.

Presto

Distributed SQL Query Engine for Big Data

Apache NiFi

An easy to use, powerful, and reliable system to process and distribute data. It supports powerful and scalable directed graphs of data routing, transformation, and system mediation logic.

Amazon Athena

Amazon Athena is an interactive query service that makes it easy to analyze data in Amazon S3 using standard SQL. Athena is serverless, so there is no infrastructure to manage, and you pay only for the queries that you run.

Related Comparisons

Some of the features offered by Apache Flink are:

Hybrid batch/streaming runtime that supports batch processing and data streaming programs.
Custom memory management to guarantee efficient, adaptive, and highly robust switching between in-memory and data processing out-of-core algorithms.
Flexible and expressive windowing semantics for data stream programs

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)

"Unified batch and stream processing" is the primary reason why developers consider Apache Flink over the competitors, whereas "It's in golang" was stated as the key factor in picking NSQ.

Apache Flink vs NSQ