Large scale web 
socket system 
TrucLK- afterlastangel@gmail.com
System Purpose 
- Scalability on public cloud infrastructure 
- Low latency command control 
- Security.
Architecture 
Amazon EC2 
IP 
Camera 
IP 
Camera 
IP 
Camera 
Server 
Server 
Server 
Web Socket Connection 
Web Socket Connection 
Web Socket Connection 
Video Stream 
TLS Authentication 
Control command
Web Socket 
DNS Load balancing App worker 
DNS query 
Scalable Architecture 
Amazon EC2 
IP 
Camera 
IP 
Camera 
App worker 
Video Stream 
Control command 
App worker 
Database 
Proxy 
worker 
Proxy 
worker 
Web Socket
DNS Load balancing 
- First load balancing. 
- Resolve concurrent TCP connections 
problem. 
- Software:
Proxy worker 
- Client authentication with TLS. 
- Sharding client with app workers. 
- Software:
App worker 
- Any web applications: Ruby, Java, Python, 
PHP … 
- Stateless with central session database.
Database 
- Does not need to be distributed 
- Should be support auto scaling 
- Suggestion: NoSQL instead of SQL
Estimation 
- Complexity : Average 
- Duration : 2 months

Large scale web socket system with AWS and Web socket

  • 1.
    Large scale web socket system TrucLK- afterlastangel@gmail.com
  • 2.
    System Purpose -Scalability on public cloud infrastructure - Low latency command control - Security.
  • 3.
    Architecture Amazon EC2 IP Camera IP Camera IP Camera Server Server Server Web Socket Connection Web Socket Connection Web Socket Connection Video Stream TLS Authentication Control command
  • 4.
    Web Socket DNSLoad balancing App worker DNS query Scalable Architecture Amazon EC2 IP Camera IP Camera App worker Video Stream Control command App worker Database Proxy worker Proxy worker Web Socket
  • 5.
    DNS Load balancing - First load balancing. - Resolve concurrent TCP connections problem. - Software:
  • 6.
    Proxy worker -Client authentication with TLS. - Sharding client with app workers. - Software:
  • 7.
    App worker -Any web applications: Ruby, Java, Python, PHP … - Stateless with central session database.
  • 8.
    Database - Doesnot need to be distributed - Should be support auto scaling - Suggestion: NoSQL instead of SQL
  • 9.
    Estimation - Complexity: Average - Duration : 2 months