In March 2021, the Mattermost server repository officially surpassed 20,000 stars on GitHub, and we couldn’t be more excited! Huge thanks to our community for their incredible support of the Mattermost open source project and their belief in the power of secure workplace messaging solutions built for developers by developers.

Users now gain the flexibility to express their current status in any way they prefer. Set a custom status to add a descriptive status message and emoji that’s visible to everyone throughout the app. Custom user statuses are available in Mattermost Cloud today and in Mattermost Self-Managed v5.33 (available March 16), with mobile support coming soon.

Mattermost is dedicated to providing effective solutions that can be utilized by as many people as possible. Accessibility is central to our core belief that chat should be simple, intuitive, and functional. For users who are visually impaired, elements such as predictable navigation are not just nice to have, but altogether necessary.

Microservices have changed the way we build applications. Software design has moved from large monolithic applications (which are not really adaptable to changes and improvements) to a collection of small, independent processes infrastructure which is far more suited to adapt to changes in today’s agile world.

One of the greatest values Mattermost provides to users is the ability to create a space for discussion, issue tracking, and succinct communication, which is made possible by administrators managing access. Our goal is to create a safe and secure communication platform for all of our users. This often comes with the need for tools to help ensure users are communicating in line with the culture of the organization or community to ensure a welcoming and inclusive experience for all.

If you’re a RabbitMQ user, chances are that you’ve seen queues growing beyond their normal size. This causes messages to get consumed long after they have been published. If you’re familiar with Kafka monitoring, you’ll call it consumer lag, but in RabbitMQ-land it’s often called queue length or queue depth.

When building Cloud applications, we often put significant effort into breaking down our monoliths into small code pieces. They are easier to maintain but hard to make them communicate together. This is where NATS comes in. NATS is a simple and highly performant messaging system for Cloud-native apps. In this talk, I will share my experience using NATS at Qovery, why you should or should not use it, and the difference between the well-known RabbitMQ and Kafka.