In this post from 2011, the creator of Omegle, Leif Brooks, explains what technology is used, including Python and a library called gevent for the backend. On top of that, Adobe Cirrus is used for streaming video. Though this post was 12 years ago, it is valuable to know what a web application like Omegle requires. A modern library that may provide some functionality for a text chat at a minimum may be... Source: 7 months ago

They might be thinking of something like ZeroMQ, which is pretty well liked: https://zeromq.org/ That said, I wouldn't call RabbitMQ that heavyweight myself, at least when compared to something like Apache Kafka. - Source: Hacker News / 8 months ago

If you want to learn message passing in an environment you're familiar with, you should check out ZeroMQ. It's a C++ lib for socket abstraction, it's immensely useful in distributed systems, it can also do in-process message passing, and it's got bindings/ports for C and Rust. Source: about 1 year ago

Inspired by the IDE language server protocol, I created an API interface between the electron and the Python ML interface. ZeroMQ turned out be an invaluable resource as a fast and lightweight messaging queue between the two. - Source: dev.to / about 1 year ago

If you really need it live, like for a chat or auctions you can use https://zeromq.org/ over websockets. Source: over 1 year ago

Sounds like you're on a good path tracking the problem to aws, not the esp. First of all, I'd try to make it work with a "proven" solution, then move on to your own implementation. I have had good success using http://mqtt-explorer.com/ on windows to diagnose a similar situation. Mqtt explorer gives you very granular control over endpoints and topics, so might be helpful to you too. Source: about 1 year ago

I would suggest using Mqtt explorer (http://mqtt-explorer.com/) to see how often the sensor updates its values. This as a first step to narrow down the problem. Source: about 1 year ago

Use MQTT Explorer to view and generate messages: http://mqtt-explorer.com/. Source: about 1 year ago

You can write test programs to send very specific messages to simulate errors, or simulate entire components that aren't written yet. There are also free programs like MQTT Explorer that will let you browse the message traffic, generate messages manually, log whatever you cant, and even graph your values if you happen to send numerical values (that is really cool when you do some long-term testing). Source: over 1 year ago

To use a local server can let you control all details of your full messaging chain. Try other clients can make you away from the ill behaviors or bugs of specific client. I recently demonstrate how easy a free MQTT client (MQTT explorer) send to a free MQTT database on Windows 10 in my video. Source: over 1 year ago