dobyte /due

A High-Performance Distributed Game Server Framework in Go

★ 990⑂ 177👁 23⑃ 20● 71▤ 60
GoMITCreated 2022-08-26dobyte.github.io/due-docs/
下载:v2.6.7v2.6.7 ↓2.6.72026-11-09
+0
日增长
990
stars
177
forks
23
watchers
20
prs
71
issues
60
releases

README

due — A High-Performance Distributed Game Server Framework in Go

English | 简体中文










!Stars
!Forks





 1. Introduction

due is an out-of-the-box, lightweight and high-performance distributed game server framework developed in Go, built on a complete native cluster solution that easily exceeds 430K+ TPS over the Gate-Node path with 500 concurrent connections on a single thread — battle-proven in multiple enterprise-level game projects, with stability fully guaranteed.
Its module design draws on the modular design philosophy of kratos, aiming to provide a complete, efficient, elegant, and standardized solution for game server development.

!Architecture

 2. Advantages

 💰 Free: The framework follows the MIT license and is fully open-source and free.
 💡 Simplicity: Simple architecture with concise, easy-to-understand source code.
 🚠 Convenience: Only the necessary APIs are exposed, reducing the mental burden on developers.
 🚀 High performance: The framework natively implements a cluster communication solution; a single thread on an ordinary machine can easily achieve 430K TPS.
 🧊 Standardization: The framework natively provides standardized development conventions, making even the most complex projects easy to handle.
 ✈️ Efficiency: The framework natively provides tcp, kcp, ws, quic and other servers, making it easy for developers to quickly build various types of gateway servers.
 ⚖️ Stability: All official releases have passed rigorous testing in real internal business scenarios, offering high stability.
 🎟️ Extensibility: Well-designed interfaces make it easy for developers to design and implement their own features.
 🔑 Smoothness: Semaphores are introduced to enable graceful rolling updates by controlling the service registry.
 🔩 Scalability: A graceful route-dispatch mechanism theoretically enables unlimited horizontal scaling.
 🔧 Easy debugging: The framework natively provides tcp, kcp, ws, quic and other clients, making it easy for developers to perform independent end-to-end debugging.
 🧰 Manageability: Complete admin APIs make it easy for developers to quickly build custom admin functionality.

 3. Features

 Gateway: Gateway servers supporting protocols such as tcp, kcp, ws, and quic.
 Logging: Multiple logging components such as console, file, aliyun, and tencent.
 Registry: Multiple service registries such as etcd, consul, nacos, and polaris.
 Protocol: Multiple communication protocols such as json, protobuf, msgpack, xml, yaml, and toml.
 Configuration: Multiple config centers such as file, etcd, consul, nacos, and polaris; also supports file formats such as json, yaml, toml, and xml.
 Communication: Multiple high-performance communication solutions such as grpc and rpcx.
 Restart: Graceful restart of servers.
 Event: Event bus implementations such as process, redis, nats, and kafka.
 Encryption: Multiple encryption and signature schemes such as rsa and ecc.
 Service: Multiple microservice solutions such as grpc and rpcx.
 Fle

Top issues

Latest release

v2.6.7 v2.6.7 2026-11-09
v2.6.7

 New Modules

- limiter: Introduce the Maker/Limiter abstraction with rule normalization, result metadata, a global maker and configurable failure policies, so rate limiting can be shared across backends. (commit)
- limiter/memory: Add a sharded in-process token bucket backend with expired-bucket eviction, bucket pooling and lifecycle management. (commit)
- limiter/redis: Add a standalone Redis backend that evaluates an atomic Lua token bucket against server time, refreshes key TTLs and supports a configurable timeout with fail-open or fail-closed behavior. (commit)
- core/limiter: Exp

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON