Enterprise Messaging Platform
Chunxiao Technology · 2014 – 2024
Role: Developer & System Designer
Cover
Android-led enterprise IM evolving from standalone tool to multi-platform system (Android/Web/PC). 5,000 DAU, sub-200ms latency, 500K+ daily messages across 5 subsystems. Migrated from legacy C++ to cloud IM, eliminating 90%+ defects. 10-year lifecycle.
5,000 DAU, <200ms latency, 500K+ msgs/day, 90%+ defect reduction, <2% downtime over 10 years
Problem
Enterprise needs reliable low-latency messaging across Android/Web/PC, with unified identity, file storage, and subsystem integration.
Solution
Cross-platform IM: NDK TCP/UDP transport for sub-200ms delivery, Spring Cloud message gateway, FastDFS distributed file storage, Easemob cloud IM migration (eliminated 90%+ defects), JPush backup push channel.
Architecture
Android NDK (TCP/UDP) + Web + PC → Nginx → Spring Cloud Message Gateway → Core Services → MySQL/Redis/FastDFS → Easemob/JPush
Key Highlights
- ▸Engineered NDK TCP/UDP transport supporting 5,000 DAU and <200ms message latency
- ▸Migrated core IM from unstable C++ to Easemob cloud, eliminating 90%+ defects
- ▸Built FastDFS distributed file storage supporting 100GB+ user uploads
- ▸Architected unified platform: user center, file service, permissions across 5+ subsystems
- ▸Integrated JPush as backup push channel alongside Easemob IM
- ▸Maintained <2% downtime across 10-year product lifecycle
Tech Stack
What I Learned
NDK TCP/UDP path essential for sub-200ms at scale; cloud migration eliminated chronic instability; manufacturer ROM push differences need layered backup channels.