Dolphin - Start secure, global instant messaging today. Private chat, group chat, low-latency audio and video calls.
Dynamics / Scan Code to add Friends / Send Files / Privatization
Deployment.
Diversified message types fully meet communication needs, stable and
secure communication capabilities, global interoperability, and rapid
deployment.

Industry
Information Technology
Information Technology
Timeline
2022 - 2023
2022 - 2023
The Challenge
The development of the IM system is a big challenge, such as
Fan-in and Fan-out issues, how to obtain new messages, how to
ensure the real-time performance of messages, how to ensure the
timing of messages, and multi-terminal synchronization and other
pain points.
Solution
This is an IM system developed internally for the client group
company. Under the premise of limited manpower, material
resources, and time resources, it usually needs to make a lot of
trade-offs. At this time, an IM system that can support rapid
iteration and easy expansion is the optimal solution. , for
security reasons, we have carried out cloud privatization
deployment.
Here is an example of how we solve pain points and difficulties:
In order to optimize the experience, for read diffusion, the synchronization of messages is mainly based on the push mode. The message ID of a single session increases sequentially. If the front-end receives the pushed message and finds that the message ID is not continuous, it requests the back-end to re-acquire the message.
In addition, our IM system adopts an asynchronous transmission confirmation mechanism, that is, as long as the message reaches the server, and then the server sends it to MQ, it will be considered successful. If the sending fails due to permissions and other issues, the backend will push a notification.
Here is an example of how we solve pain points and difficulties:
In order to optimize the experience, for read diffusion, the synchronization of messages is mainly based on the push mode. The message ID of a single session increases sequentially. If the front-end receives the pushed message and finds that the message ID is not continuous, it requests the back-end to re-acquire the message.
In addition, our IM system adopts an asynchronous transmission confirmation mechanism, that is, as long as the message reaches the server, and then the server sends it to MQ, it will be considered successful. If the sending fails due to permissions and other issues, the backend will push a notification.



