link1st/gowebsocket

golang基于websocket单台机器支持百万连接分布式聊天(IM)系统

View on GitHub ↗Jump to charts ↓

link1st/gowebsocket has 3k+ stars and 600+ forks on GitHub, is written in Go, and was last pushed on Sep 21, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 31 minutes ago
Added to GitGenius on September 22nd, 2026
Created on July 29th, 2019
Open Issues & Pull Requests: 2 (+0)
GitHub issues: Enabled
Number of forks: 635
Total Stargazers: 3,106 (+0)
Total Subscribers: 57 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.7 days
Mean response time: 674.6 days
90th percentile: 1344.6 days
Tracked items: 2

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,677 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

gowebsocket is a distributed instant messaging system built on WebSocket that supports millions of concurrent connections on a single machine.

The project addresses the challenge of building scalable real-time communication infrastructure by implementing WebSocket communication in Go with architectural patterns designed for high concurrency. It uses the Gin framework for HTTP handling, Nginx for load balancing, and gRPC for inter-service communication between distributed nodes. The approach enables horizontal scaling across multiple machines while maintaining efficient message routing between connected clients.

Teams building chat or instant messaging systems should consider this tool if they need to handle large numbers of concurrent WebSocket connections and want to scale horizontally. The project is suited for applications requiring real-time bidirectional communication with distributed deployment capabilities. It demonstrates practical patterns for managing millions of connections per node and coordinating message delivery across a cluster of servers.

The project shows consistent engagement with issues being opened and closed, indicating active maintenance and responsiveness to problems raised by users.