Apache ActiveMQ vs Faye

Apache ActiveMQ is an open-source messaging and Integration Patterns server for applications that exchange messages. It is self-hosted and supports OpenWire, STOMP, AMQP 1.0, MQTT 3.1, and REST. Listed client languages include Java, C, C++, C#, Ruby, Perl, Python, and PHP. Messaging features include message groups, virtual and composite destinations, wildcards, and enterprise integration patterns. ActiveMQ fully supports JMS 1.1 and J2EE 1.4+ messaging, including transient, persistent, transactional, and XA modes; support for Jakarta Messaging 3.1 and JMS 2.0 is partial. Transport options include in-VM, TCP, SSL, NIO, UDP, multicast, JGroups, and JXTA, with JDBC persistence and a high-performance journal. Browser access is available through a REST API and Ajax web streaming. Security options include pluggable providers, JAAS authentication, XML-configured authorization, and user, group, and destination permissions. ActiveMQ Classic costs nothing under the Apache License 2.0.

Faye is a publish-subscribe messaging system that uses the Bayeux protocol. It provides message servers for Node.js and Ruby, plus clients for servers and major web browsers. Browser clients rely on a Faye server to relay messages; they can retry after a lost connection and redeliver dropped messages. Transport adapters cover WebSocket, HTTP long-polling, Cross Origin Resource Sharing, and JSON-P callback-polling. Server and client extensions can intercept or modify messages, including to add subscription authentication. The monitoring API reports handshakes, subscriptions, unsubscriptions, publishes, and disconnections. Faye runs on Linux, macOS, and Windows, and can be self-hosted. Its default in-process engine cannot span multiple front-end web servers, but Redis and Couchbase engines are documented for distributed deployments. Faye is free and open source under the Apache 2.0 license; the listed plan is free. Install the Node.js server through npm or the Ruby server through RubyGems.