Faye vs WCF

Overview

Faye

Stacks29

Followers34

Votes24

GitHub Stars4.4K

Forks369

WCF

Stacks125

Followers107

Votes5

Faye vs WCF: What are the differences?

Faye: Simple pub/sub messaging for the web. Faye is a set of tools for simple publish-subscribe messaging between web clients. It ships with easy-to-use message routing servers for Node.js and Rack applications, and clients that can be used on the server and in the browser; WCF: 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.

Faye and WCF can be primarily classified as "Realtime Backend / API" tools.

Faye is an open source tool with 4.2K GitHub stars and 386 GitHub forks. Here's a link to Faye's open source repository on GitHub.

According to the StackShare community, WCF has a broader approval, being mentioned in 8 company stacks & 3 developers stacks; compared to Faye, which is listed in 5 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

Faye	WCF
Faye is a set of tools for simple publish-subscribe messaging between web clients. It ships with easy-to-use message routing servers for Node.js and Rack applications, and clients that can be used on the server and in the browser.	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
GitHub Stars 4.4K	GitHub Stars -
GitHub Forks 369	GitHub Forks -
Stacks 29	Stacks 125
Followers 34	Followers 107
Votes 24	Votes 5
Pros & Cons
Pros 6 Simple 5 Open source 5 Node.js 2 BAYEUX Protocol (not proprietary) 2 Real-time	Pros 5 Classes

What are some alternatives to Faye, 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.