NATS vs WCF

Overview

NATS

Stacks393

Followers498

Votes60

WCF

Stacks125

Followers107

Votes5

NATS vs WCF: What are the differences?

Developers describe NATS as "Lightweight publish-subscribe & distributed queueing messaging system". Unlike traditional enterprise messaging systems, NATS has an always-on dial tone that does whatever it takes to remain available. This forms a great base for building modern, reliable, and scalable cloud and distributed systems. On the other hand, WCF is detailed as "A runtime and a set of APIs for building connected, service-oriented applications". It is a framework for building service-oriented applications. Using this, you can send data as asynchronous messages from one service endpoint to another. A service endpoint can be part of a continuously available service hosted by IIS, or it can be a service hosted in an application.

NATS and WCF belong to "Realtime Backend / API" category of the tech stack.

Apcera, Workiva, and Bridgevine are some of the popular companies that use NATS, whereas WCF is used by Bluebeam Software, Heimdal Security, and KGS Buildings. NATS has a broader approval, being mentioned in 26 company stacks & 12 developers stacks; compared to WCF, which is listed in 8 company stacks and 3 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

Detailed Comparison

NATS	WCF
Unlike traditional enterprise messaging systems, NATS has an always-on dial tone that does whatever it takes to remain available. This forms a great base for building modern, reliable, and scalable cloud and distributed systems.	It is a framework for building service-oriented applications. Using this, you can send data as asynchronous messages from one service endpoint to another. A service endpoint can be part of a continuously available service hosted by IIS, or it can be a service hosted in an application.
Statistics
Stacks 393	Stacks 125
Followers 498	Followers 107
Votes 60	Votes 5
Pros & Cons
Pros 22 Fastest pub-sub system out there 16 Rock solid 12 Easy to grasp 4 Light-weight 4 Easy, Fast, Secure Cons 2 Persistence with Jetstream supported 1 No Persistence 1 No Order	Pros 5 Classes

What are some alternatives to NATS, WCF?

Firebase

Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds.

Socket.IO

It enables real-time bidirectional event-based communication. It works on every platform, browser or device, focusing equally on reliability and speed.

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.

PubNub

PubNub makes it easy for you to add real-time capabilities to your apps, without worrying about the infrastructure. Build apps that allow your users to engage in real-time across mobile, browser, desktop and server.

Pusher

Pusher is the category leader in delightful APIs for app developers building communication and collaboration features.

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.

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.

SignalR

SignalR allows bi-directional communication between server and client. Servers can now push content to connected clients instantly as it becomes available. SignalR supports Web Sockets, and falls back to other compatible techniques for older browsers. SignalR includes APIs for connection management (for instance, connect and disconnect events), grouping connections, and authorization.