So, we develop a chat application where the end-users types the text, sends the messages, it gets validated in the database and reaches the client-server.
It lacks in DBA (Database Administrator)
Lacks in the top-notch Database to scale concurrent users.
The Architecture of An Enterprise Chat Application
It’s the architecture of MirrorFly - An enterprise chat application built on Erlang, transmitting information on XMPP protocol, ejabberd server and storing on Mnesia database.
It supports TCP/TLS connections as well as UDP transport, as is described in our last discussions.
Among the new software updates, Google is finally rolling out its long debuted RCS chat service after waiting a lot for the carriers which were dragging the collective feet or not acting at pace.
When even after pushing the carriers valiantly, they do not speed up the process of offering support for RCS chat, Google independently takes the bold move of providing the new texting experience to the Android users.
Due to point-driven model, when the message is sent to the chat-ready phone or the phone that’s not chat-ready, but device and carrier support RCS, then the RCS message will be delivered to the intended user.
The service is using the phone number to send messages to the users.
The web interface can be enabled with QR code scanning, but its use is limited to message editing, not as a secondary device to communicate.
It offers everything for which the users are looking to switch to iPhone or download WhatsApp or Facebook messenger app.