Tiledesk new messaging engine, moving from Firebase to MQTT / RabbitMQ
Actually Tiledesk uses Firebase to deliver messages in real time between all the components of the platform (console, web widget, mobile apps etc.) that directly need to exchange messages. We have a big announcement for our open source community: we are planning to move to a new messaging engine 🤗🤗🤗
Tiledesk uses the Chat21 chat platform, an open source set of applications, free to use, built and maintained by our Company.Messages are stored both in the Tiledesk database (for analytics, full text search features etc.) and Firebase (just to allow the client apps – ex. iOS App – to get the conversation messages history).
Here you can find a description of the current Architecture.
The blue frame, Chat21 server, is deployed on Firebase cloud, and is built using Firebase Realtime DB + Firebase Cloud functions.Every Client is connected through websockets with Chat21 Server. A mix of events on messages and webhook calls will synchronize Chat21 Server with Tiledesk server. All messages actually are stored on both platforms for different purposes.
The new messaging engine
The next Tiledesk platform release will have a new, pluggable instant messaging engine, based on RabbitMQ (server component) and MQTT protocol (Firebase will still be still supported).The next version will be released for production in April.
In the new version, the blue frame will be a RabbitMQ instance that will only deliver messages, only storing them for the sole mission of delivering.
Once delivered, a message is removed from the delivering queue.With the new version messages will only be stored in Tiledesk where it will be easier to manage them applying to each message the policies chosen by the data owner.
Moreover, with the new Tiledesk version, the messaging engine will be pluggable, so everyone can unplug from our RabbitMQ solution, choosing another engine.
Enjoy Tiledesk and don’t forget to check our blog for the latest news!
