WebSockets and RabbitMQ: Web-STOMP, (...)
summary
Benchmarks compare RabbitMQ’s web_stomp plugin, web_mqtt plugin, and AMQP over WebSockets via an open‑source web socket TCP relay (used on CloudAMQP dedicated plans). Results show web‑mqtt handles ~13,000 connections on a 2‑CPU/4GB node versus ~9–10k for web_stomp and web_amqp; on 8GB nodes MQTT still uses less memory though CPU is similar. Erlang process counts differ: one process per connection for web‑mqtt, many more for web_amqp and web_stomp. Recommendation: prefer web_mqtt for lightweight clients, use web_amqp when already using AMQP, use web_stomp only if STOMP is required.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:03Evolution of the Web
- 2:46Messaging Protocols
- 3:38Combining Tools
- 5:59WebSocket Relays
- 9:14Benchmarking Results
- 15:05Protocol Selection
related talks
15mMQTT and Node.js Messaging the Internet of Things
20mRabbitMQ and PM2 in Node.js for managing Multiple Processes
58mSSE vs WebSockets vs Long Polling
41mWebsockets as the glue to interactivity
01h 30mDeep dive into Spring WebSockets
49mThe Real Time Web with XMPP
41mWeb | C++
35mServerless WebSockets at Scale