Tagged articles
IM
31 articles · Page 1 of 1
This article analyses why MQTT over RabbitMQ is a better foundation than a custom WebSocket service for large‑scale instant‑messaging systems, detailing connection management, message routing, session handling, QoS, retained and will messages, topic design, Go client implementation, bridge service logic, scaling challenges, monitoring, and migration road‑maps.
GoIMKubernetes
0 likes · 40 min read


ITPUBJul 28, 2025 · Backend Development
This article explains the three types of IM packets—Request, Acknowledge, and Notify—illustrates the basic message flow between client and server, identifies reliability gaps such as lost notifications, and proposes an application‑level solution using acknowledgments, timeout‑driven retransmission, and message deduplication to achieve dependable delivery.
IMMessage Reliabilityacknowledgment
0 likes · 8 min read

This article walks through creating a distributed instant‑messaging system in Go, covering the full tech stack, Docker‑based and local startup methods, configuration files, the end‑to‑end request flow, and detailed code examples for RPC, Redis queues, WebSocket delivery and the internal bucket architecture.
DockerGinIM
0 likes · 17 min read

This article explains the fundamentals of Remote Procedure Call (RPC), why it is crucial for developing production‑grade instant‑messaging clusters, how it differs from plain HTTP, the typical RPC call flow, common frameworks such as gRPC, Thrift and Dubbo, and practical considerations for high‑throughput distributed systems.
IMRPCbackend development
0 likes · 12 min read

This article dissects the end‑to‑end technical workflow of sending a customer‑service IM message, covering reliability, real‑time delivery, ordering, idempotency, performance bottlenecks, async handling, requestAnimationFrame, protobuf migration, and user‑experience optimizations, while sharing concrete metrics and real‑world solutions.
IMProtobuffrontend
0 likes · 24 min read

The article examines the end‑to‑end technical and design challenges of delivering a single customer‑service instant‑message, detailing reliability, ordering, idempotency, performance optimizations such as async handling and binary‑search traversal, security practices, latency reductions via Protocol Buffers, and a roadmap for future enhancements.
Frontend OptimizationIMMessage Reliability
0 likes · 20 min read

This article breaks down the functional requirements, data models, layered architecture, push‑pull messaging choices, and message flow for building a robust one‑to‑one instant‑messaging service using Redis, MySQL and asynchronous queues.
Chat ArchitectureIMMessage Queue
0 likes · 13 min read


HomeTechDec 6, 2022 · Backend Development
This article details the architectural decisions, network protocol choices, message framing strategies, and server‑level optimizations—including Netty adoption, TCP handling, token management, load balancing, NIC queue configuration, and CPU affinity—that enable a scalable, low‑latency instant messaging service supporting millions of concurrent connections.
BackendIMNetty
0 likes · 19 min read

The article explains why a custom instant‑messaging SDK was built for a customer‑service web client, outlines its three‑layer architecture (WebSocket/gRPC network, RxJS‑driven data‑link, and application logic), and details reliability features such as ACKs, retries, deduplication, and ordering to improve performance, stability, and scalability.
IMMessage ReliabilitySDK
0 likes · 14 min read

The article explains NetEase Cloud IM's "Circle Group" product, detailing its massive relationship complexity and scale, the technical challenges it creates, and the layered backend architecture and mechanisms designed to handle multi‑entity coupling, huge member volumes, and efficient change notifications.
IMbackend developmentcloud services
0 likes · 13 min read

This article details how the Beike instant‑messaging system was analyzed, bottlenecks identified, and a series of backend optimizations—including business isolation, increased concurrency, computation reduction, and Redis connection‑pool redesign—were applied to boost 300‑person group‑chat throughput from 15 QPS to over 320 QPS, achieving more than a twenty‑fold performance gain.
GoIMRedis
0 likes · 12 min read

The Xianyu instant‑messaging system, burdened by years of technical debt, was rebuilt with a Flutter‑centric, four‑layer architecture that shares FlutterEngine instances, introduces an entity cache and custom ORM, simplifies synchronization, and delivers up to 40 MB memory savings, lower power use, reduced CPU load and roughly half the development and testing effort.
FlutterIMarchitecture
0 likes · 11 min read

This article chronicles the development of Ctrip’s internal office IM from its 2016 inception to the current TripPal open platform, detailing its architectural evolution, high‑availability and performance optimizations across gateway, identity, microservice, and IM layers, and outlines future directions for open‑platform services.

This article explains the overall architecture, data structures, login and messaging flows, common real‑time, reliability and consistency challenges, and high‑availability and high‑concurrency techniques used in a production instant‑messaging service.
BackendIMarchitecture
0 likes · 13 min read

Xianyu improved its online IM channel stability by adding heartbeat‑based connection monitoring, rapid reconnection, ACK‑driven retry queues stored in Alibaba Cloud Table Store, and adaptive delay strategies, which together cut ACC compensation arrival time by 75% (from 60 to 15 minutes) and dramatically reduced user complaints.
IMLong ConnectionMessage Retransmission
0 likes · 14 min read

Xianyu IM’s data‑sync was re‑engineered by extracting a dedicated sync layer that uses domain‑based versioning, push‑pull hybrid buffering, and priority queues, decoupling business logic, eliminating redundant pushes, and achieving a 31% latency reduction and 35% traffic savings while enabling dynamic priority adjustments.
IMLayered Architecturedata synchronization
0 likes · 10 min read

This article analyses the architecture of high‑traffic instant‑messaging services such as WeChat and Momo, detailing long‑connection handling, short‑vs‑long HTTP/TCP protocols, custom binary messaging, smart routing, load‑balancing, sharding, replication, and the engineering trade‑offs required for massive scalability and reliability.
IMdistributed systemsprotocol
0 likes · 12 min read


58 TechDec 13, 2019 · Mobile Development
This article describes the redesign of a large‑scale Android instant‑messaging (IM) module, detailing the shortcomings of the original architecture, the new three‑layer framework, the split‑converter for parallel business‑line development, component‑based UI design, and the design‑pattern techniques used to achieve a maintainable, extensible solution.
AndroidComponentizationIM
0 likes · 16 min read


58 TechDec 4, 2019 · Backend Development
The article summarizes the second 58.com instant‑messaging technology salon, detailing the architecture, high‑performance long‑connection design, multi‑thread socket models, read‑write diffusion storage strategies for single‑ and group‑chat, message synchronization mechanisms, and the IM SDK framework for audio‑video communication.
IMLong ConnectionMessage Storage
0 likes · 20 min read

This article analyzes why instant‑messaging (IM) messages can arrive out of order due to time discrepancies, network behavior, and multithreading, and proposes a comprehensive design using global sequence numbers, channel‑aware routing, client‑side caching, and ACK‑based flow control to guarantee ordered delivery.
BackendIMSequence Number
0 likes · 9 min read

The article details the step‑by‑step architectural evolution of Mafengwo's instant‑messaging platform—from an initial PHP‑based monolith, through polling optimizations with OpenResty, to a Go‑implemented, micro‑service‑oriented design that improves scalability, reliability, and multi‑device synchronization.
GoIMOpenResty
0 likes · 14 min read

This guide introduces Bitchat, a Netty‑based IM framework, showing how to start the server and client, use built‑in commands for login, user listing and private messaging, explains its architecture, custom protocol, health‑check mechanisms, and how to handle business logic with asynchronous thread pools.
ClientIMJava
0 likes · 12 min read

This article chronicles the evolution of MaFengWo's instant‑messaging platform, detailing the transition from a simple PHP implementation to OpenResty optimizations, the introduction of multi‑mode routing in IM 2.0, and a complete service‑oriented redesign in Go for IM 3.0, while addressing scalability, multi‑device synchronization, and message reliability.
GoIMOpenResty
0 likes · 14 min read

This article presents a comprehensive design and implementation of a high‑availability, horizontally scalable instant‑messaging group‑chat system, detailing its architecture, component interactions, scaling strategies, reliability mechanisms, and extensions for offline and single‑chat messaging.
High AvailabilityIMgroup chat
0 likes · 48 min read

This article explains the evolution from traditional to modern instant‑messaging system architectures, introduces a Timeline logical model for message sync and storage, discusses read‑ and write‑diffusion strategies, evaluates database requirements, and demonstrates a TableStore‑based implementation with sample code.
IMTablestoredistributed systems
0 likes · 14 min read


58 TechSep 19, 2018 · Backend Development
The article explains the MicroChat instant‑messaging backend architecture, detailing its long‑connection, access, logic, and storage layers, and describes how message synchronization, offline handling, hole‑filling, unread count roaming, and read receipts are implemented and optimized for multi‑device use.
IMRead Receiptsbackend architecture
0 likes · 15 min read


21CTONov 17, 2017 · Backend Development
This article explains the evolution of instant messaging systems, introduces the Timeline logical model for message synchronization and storage, compares traditional and modern architectures, and details how Alibaba Cloud TableStore can be used to build a high‑performance, multi‑device IM backend supporting millions of TPS and millisecond latency.
IMMessage SyncNoSQL
0 likes · 15 min read


21CTOApr 10, 2016 · Backend Development
This article details how 58.com’s 58‑BangBang service evolved through four architectural stages—from a traditional instant‑messaging system to a mobile‑push enabled platform—addressing massive traffic, scalability, and integration challenges across IM, merchant management, and mobile marketing.
BackendIMmobile-push
0 likes · 13 min read


ITPUBDec 2, 2015 · Backend Development
This article details a backend redesign of an instant‑messaging platform, covering Java interfaces for unread messages, Redis‑based unread counters, persistent queue processing, MySQL sharding and partitioning, SQL retrieval logic, and performance tuning to achieve high insert throughput.
IMMessage QueueMySQL
0 likes · 9 min read


21CTOSep 10, 2015 · Backend Development
Sun Xuan, a system architect at 58.com, details the evolution of the company's merchant mobile management platform—from its early IM‑centric design through third‑party service integration to a lightweight client architecture—while also dissecting core O2O technologies such as long‑connection push, LBS, and cross‑platform notification strategies.
IMbackend architecturemobile O2O
0 likes · 9 min read

This article explains how web instant‑messaging systems achieve reliable, non‑lost and non‑duplicate message delivery by using a six‑message protocol (msg R/A/N and ack R/A/N), timeout‑based retransmission, and deduplication mechanisms.
Ack ProtocolIMMessage Delivery
0 likes · 8 min read
