How NetEase Cloud IM Solves Massive Group Relationships: Architecture & Challenges
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.
Business Features
NetEase Cloud IM's new "Circle Group" product serves massive social communities, with relationship complexity (multiple entities, varied management mechanisms, heavy coupling) and huge scale (member counts and change batches reaching millions).
Technical Challenges
The system faces two main difficulties: complex business logic due to multi‑entity, multi‑management hierarchical coupling, and massive processing overhead caused by millions of members and batch changes.
Business Logic Complexity
Multi‑level structure (servers, channels, channel groups) creates cascading updates.
Identity groups introduce group‑wide member changes.
Various member management mechanisms (invite/apply, public/private with black/white lists) add further coupling.
Processing Complexity
Member‑size storage, network transmission and cache become huge.
Batch change operations can involve millions of linked updates, consuming extensive time and resources.
Notification broadcasting must deliver millions of change messages efficiently.
Overall Architecture
The solution adopts a layered architecture:
Client layer – mobile, desktop SDKs and OpenAPI.
Access layer – LBS, long‑connection service, API gateway.
Network layer – proprietary global real‑time transport network WE‑CAN.
Business layer – App services for SDK processing and WebServer services for OpenAPI.
Service layer – login, messaging, relationship, identity‑group, support modules, each composed of micro‑services.
Infrastructure layer – databases and middleware.
Technical Details
Channel Member Management
A two‑phase approach separates final state persistence from transitional computation, and an ordered asynchronous parallel event processing mechanism ensures correct, low‑latency updates despite massive coupling.
Change Notification Broadcast
Notifications are classified into participants (must receive) and observers (receive based on subscription). An online broadcast subscription model lets clients pull changed data instead of receiving full data, dramatically reducing compute and bandwidth costs while supporting horizontal scaling.
Cloud‑Side Relationship Data Retrieval
To avoid full‑copy queries, the system provides cloud‑based search for servers, channels and members, supporting both public “square” searches and internal searches with flexible sorting.
Conclusion
NetEase Cloud IM's "Circle Group" offers a clean‑slate, highly scalable design that can power Discord‑like social or gaming applications.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
NetEase Smart Enterprise Tech+
Get cutting-edge insights from NetEase's CTO, access the most valuable tech knowledge, and learn NetEase's latest best practices. NetEase Smart Enterprise Tech+ helps you grow from a thinker into a tech expert.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.