Live Streaming Chat Room
Chunxiao Technology · 2013 – 2015
Role: Full-stack Developer (Web + Android + Server)
Cover
1 / 2The company's earliest product — a live streaming chat room platform built during the start-up phase before pivoting to IoT. 8-person team. I built: ASP.NET/DNN monolithic admin backend (no front/back separation), a Node.js + Socket.IO web chat room with HTML5 M3U8 video playback, and the Android client. Also contributed to the C++ server core. Server was rewritten multiple times. Company exited this business in 2015.
1,000+
Peak Concurrent
99.5%
Uptime
2 years
Duration
8
Team Size
5+
Languages
Problem
Early-stage start-up needed a live streaming chat room platform with real-time messaging, room management, and audio/video streaming across web and mobile.
Solution
Full-stack platform: ASP.NET/DNN monolithic backend for management, C++ server core for messaging/streaming (rewritten multiple times), Node.js + Socket.IO web client with HTML5 M3U8 video, Android mobile client. RTMP ingest with HLS delivery for cross-platform playback.
Architecture
ASP.NET/DNN Admin + C++ Server Core (RTMP/HLS) → Node.js Socket.IO Web Client + Android Client
Key Highlights
- ▸Built ASP.NET/DNN monolithic management backend (server-side rendered, no front/back separation) for stream and user admin
- ▸Developed Node.js + Socket.IO web chat room with HTML5 M3U8 video playback
- ▸Delivered Android client for live streaming and chat interaction
- ▸Contributed to C++ server core across multiple architecture rewrites
- ▸Server core was rewritten multiple times as the team iterated on the architecture during start-up phase
Tech Stack
What I Learned
Start-ups ship fast and iterate — the server was rewritten multiple times as the team figured out the right architecture. Monolithic server-side rendering (DNN/ASP.NET) was the standard before front/back separation became mainstream. Cross-platform (web + Android) with a unified C++ core was the right call for streaming performance.