Real-time Stack Issue #21

ProcessOne
· 1 min read
Send by email

ProcessOne curates two monthly newsletters – tech-focused Real-time Stack and business-focused Real-time Enterprise. Here are the articles concerning tech aspects of real-time development we found interesting in Issue #21. To receive this newsletter straight in your inbox on the day it’s published, subscribe here.

Releasing ejabberd 19.02: the MQTT Edition

This new ejabberd 19.02 release includes new major features, but also several improvements and bug fixes. The biggest news is the introduction of MQTT support.

Introducing Fluux: XMPP & MQTT as a Service

Today, we are rebranding and expanding our well-received ejabberd SaaS platform! The new name is Fluux, supporting both XMPP & MQTT, in the cloud, as a single service with a unique and simple business model.

Introduction to MQTT with IoT Studio

MQTT is one of the main protocol designed to power the Internet of Things. In this talk, we introduce the concepts being MQTT protocol design. If you have any questions regarding MQTT or suggestions of topics for the next IoT Studio videos, please let us know in the comments.

HTTP Recorder and Mock Library

If you need to write tests for code involving lot of API and web page scrapping, you often end up saving pages as fixtures and loading those fixtures to try injecting them in your code to simulate the query.

Install Ejabberd on CentOS 7

In today’s age, the age of security, many organizations like to have control of their communications. Fortunately, they have an open, secure and reliable protocol like XMPP.

MQTT Client Load Balancing With RabbitMQ and Spring Cloud

MQTT is a machine-to-machine (M2M), IoT connectivity protocol. It was designed as an extremely lightweight publish and subscribe messaging transport. It is useful for connections with remote locations where a small code footprint is required and/or network bandwidth is at a premium.

No, the Problem Isn’t “Bad Coders”

In this article, the author is going to look at a recent bug that was caught by the Rust compiler, which shows that not only is this assertion unreasonable but virtually impossible for reasons that haven’t been discussed.