Tagged articles
game server
35 articles · Page 1 of 1
A client-side team with zero game development experience used AI to prototype, build, and launch a multiplayer pool game inside a live streaming app, solving challenges in game logic, real-time server synchronization, art production, and deployment to achieve top-three engagement in its first week.
AI-assisted developmentfragment shadergame development
0 likes · 19 min read

This article explains how cloud‑native game services can achieve precise, state‑aware connection management and graceful shutdown by combining OpenKruiseGame with a cloud‑native API gateway, detailing the challenges of seven‑layer networking, the custom lifecycle hooks, deployment steps, and the benefits of zero‑downtime configuration changes.
API GatewayConnection ManagementOpenKruiseGame
0 likes · 11 min read

The article explains how the combination of a cloud‑native API gateway and OpenKruiseGame (OKG) addresses the "last mile" of game connection governance by providing fine‑grained state awareness, graceful server shutdown, and zero‑downtime configuration changes, all without intrusive modifications to existing business architecture.
API GatewayKubernetescloud-native
0 likes · 12 min read

This article explains how to design a cloud‑native architecture that assigns fixed external addresses to individual game‑server pods in Kubernetes, allowing players to connect directly via CLB, EIP, or API Gateway, and describes the necessary Volcengine components and configuration steps.
Direct ConnectionKubernetesgame server
0 likes · 11 min read

This guide explains how to implement a custom TCP protocol in PHP using Workerman for Unity3D multiplayer games, covering the sticky‑packet problem, protocol interface methods, two concrete protocol examples, and step‑by‑step testing of packet framing and splitting.
PHPSticky PacketsTCP
0 likes · 9 min read

Although microservices are popular for many applications, this article explains why game servers often avoid them, citing real‑time latency requirements, stateful processing, high network overhead, and the difficulty of maintaining fast, low‑latency communication, while also interspersing promotional content for ChatGPT services.
backend architecturegame serverreal-time performance
0 likes · 11 min read

The article explains why many game server architectures resist adopting microservices, highlighting the critical need for ultra‑low latency, stateful communication, and high‑performance networking that microservice overhead and stateless designs can jeopardize.
Real-timegame serverstateful services
0 likes · 10 min read

This guide shows how to use Alibaba Cloud Container Compute Service (ACS) to create a private Palworld game server with Kubernetes resources, cost‑effective serverless scaling, and optional best‑effort instances, including step‑by‑step commands and YAML configurations.
Alibaba CloudContainer ComputeCost Optimization
0 likes · 10 min read

This guide walks you through setting up a Palworld private server on a cloud VM by preparing an Ubuntu/Debian machine, installing SteamCMD, creating a dedicated user, downloading and configuring PalServer, opening port 8211, and launching it with nohup, plus troubleshooting tips.
LinuxPalworldSteamCMD
0 likes · 12 min read

In a recent interview with a listed game company, the author explores why microservice architectures, despite their popularity for scalable web applications, often clash with the low‑latency, state‑heavy requirements of real‑time game servers, highlighting technical and team‑size considerations.
Real-timebackend architecturegame server
0 likes · 8 min read

A developer shares insights from a game company interview, explaining why microservice architectures often clash with the low‑latency, state‑heavy requirements of real‑time multiplayer games and when they might still be appropriate.
BackendReal-timearchitecture
0 likes · 9 min read

This step‑by‑step guide shows how to install Java, configure a Minecraft Java Edition server on Windows, create a startup batch file, adjust server properties, test LAN connectivity, and use cpolar to create a public TCP tunnel (including a fixed address) for remote gameplay without needing a public IP.
Java serverMinecraftWindows
0 likes · 9 min read

This article examines why game companies' servers often avoid microservice architectures, emphasizing the real‑time latency, stateful processing, and networking constraints that make traditional microservice approaches unsuitable for high‑performance game back‑ends and why alternative designs such as custom TCP solutions or stateful server clusters are preferred.
NetworkingReal-timebackend architecture
0 likes · 8 min read

A technical discussion explains that game servers prioritize ultra‑low latency and stateful in‑memory communication, making micro‑service architectures impractical despite their benefits for modularity and scaling, especially in fast‑paced MOBA titles.
Real-timeStatefulbackend architecture
0 likes · 9 min read

This article walks through embedding the V8 JavaScript engine into a C++ game server, demonstrates a HelloWorld example, shows how to bind C++ classes using Puerts, and explains how to compile and embed a full Node.js runtime, with complete code snippets and a GitHub repository link.
C++EmbeddingJavaScript
0 likes · 11 min read

The article analyzes why many game server architectures avoid microservices, highlighting real‑time latency requirements, stateful processing, network overhead, and the mismatch between typical microservice patterns and the high‑performance demands of multiplayer online battle arena games.
Real-timebackend architecturedistributed systems
0 likes · 9 min read

The article explains that game servers, especially real‑time multiplayer titles, avoid microservices because the added network overhead, stateful communication requirements, and strict latency constraints make monolithic or tightly coupled designs more suitable for high‑performance gameplay.
Real-timeStatefularchitecture
0 likes · 8 min read

The article explains, through interview excerpts, why many game studios avoid microservice architectures for their real‑time servers, highlighting latency‑sensitive communication, stateful processing, and the overhead of distributed networking that conflict with the performance demands of modern multiplayer games.
BackendReal-timearchitecture
0 likes · 8 min read

The article explains that game servers, especially for fast‑paced multiplayer titles, avoid microservice architectures because real‑time latency, stateful in‑memory processing, and high‑performance networking requirements make the added overhead and complexity of microservices unsuitable.
Real-timegame server
0 likes · 8 min read

This article examines why many game companies avoid microservice architectures, highlighting the real‑time latency, stateful memory requirements, and networking constraints that make traditional microservice patterns unsuitable for fast, multiplayer game servers.
Real-timebackend architecturedistributed systems
0 likes · 8 min read

This article analyzes the challenges of low‑latency, stable, and cost‑effective online multiplayer games and explains how Tencent's Game Server Engine (GSE) provides elastic scaling, near‑by scheduling, stateful shrinkage, multi‑region disaster recovery, and zero‑downtime updates to meet those demands.
Elastic ScalingTencent GSEcloud gaming
0 likes · 11 min read

A game server bug caused hundreds of reward emails to be sent on New Year's Day because a copied Java date‑difference function returned incorrect values for cross‑year dates, and the issue was resolved by replacing it with a reliable Java 8 time API implementation.
Java8bug fixcode-review
0 likes · 6 min read


21CTOAug 15, 2017 · Game Development
This article traces the evolution of game server architectures across seven types, from early weak‑interaction HTTP servers and the first MUD systems to modern seamless, dynamically balanced, and P2P‑enabled back‑ends, highlighting design choices, scalability challenges, and practical implementation details.
MMOarchitecturegame server
0 likes · 19 min read


21CTOJul 12, 2017 · Backend Development
This article outlines the principles and components of a scalable game server architecture, covering login management, region selection, gateway handling, communication protocols, publish‑subscribe, RPC, server merging, and the evolution from single‑threaded to cloud‑native designs.
architecturebackend developmentdistributed systems
0 likes · 24 min read

This article outlines a four‑layer game server framework—including gateway, logic, record, and database services—detailing their responsibilities, implementation models such as multithreaded reactors and coroutine libraries, service‑driven designs, and the common design patterns and algorithms used in backend game development.
Algorithmsbackend architecturegame server
0 likes · 6 min read

This article details how Tencent Games built, customized, and continuously optimized a Kubernetes‑based container platform over three years to support tens of thousands of game containers, covering deployment modes, scheduler enhancements, network solutions, resource quotas, monitoring, storage, and the transition to micro‑service architectures.
ContainerizationKubernetescloud-native
0 likes · 19 min read

Game server development suffers from generic client‑communication tools and inadequate data stores, leading to duplicated, latency‑heavy code, so a purpose‑built, memory‑resident distributed cache that persists locally and eliminates serialization boiler‑plate is essential for real‑time, low‑latency gameplay.
Cachingdata architecturegame server
0 likes · 12 min read

This article explains how to design and implement a simple game server framework, covering the definition of server development, the two main game‑server architectures, core scene‑service requirements, a lightweight network library built on sockets, and sample C# code for connectors, server and client networking components.
C++Socketframework
0 likes · 14 min read

This article examines how to maintain game world state using data services, discussing traditional DB proxy processes, the role of Redis as a cache and database, stateless versus stateful services, sharding, high‑availability mechanisms such as Sentinel, Zookeeper, and the overall architecture for scalable MMO back‑ends.
Data ServiceHigh AvailabilityRedis
0 likes · 32 min read

The article examines common misconceptions about game server performance, outlines essential message pipelines, introduces Gate as a reverse‑proxy for low‑latency scene synchronization, discusses integrating a message‑queue (MQ) for decoupled services, and presents a service‑oriented RPC framework with patterns to build maintainable, scalable multiplayer back‑ends.
GateMessage QueueNetworking
0 likes · 34 min read

This article details how a Tencent game operations team reduced a major online game's scheduled maintenance window from 1.5 hours to just 0.3 hours by redesigning the checklist, separating pre‑ and post‑maintenance tasks, and switching to a rename‑based update method across thousands of servers.
OperationsProcess Optimizationdowntime reduction
0 likes · 10 min read

This article traces the historical progression of game server architectures—from simple HTTP‑based servers for low‑interaction mobile games, through the first‑generation MUDOS engine, second‑generation database‑driven designs, third‑generation seamless world nodes with dynamic load balancing, to specialized Battle.net, casual, and modern action MMO server models—highlighting the technical motivations and challenges at each stage.
MMONetworkingdistributed systems
0 likes · 18 min read

This article surveys the progression of game server architectures across eight types, detailing how early text‑based MUD servers evolved through multi‑threaded, distributed, and seamless‑world designs to modern hybrid action/MMO back‑ends, highlighting key technologies, scaling strategies, and architectural trade‑offs.
MMOarchitecturegame server
0 likes · 19 min read


21CTOJan 18, 2016 · Backend Development
This article traces the development of game server architectures from early text‑based MUD systems through first‑generation HTTP‑based services for simple card and runner games, to the complex, distributed backend designs used by modern MMORPGs, highlighting key technologies, design choices, and scaling challenges.
MMOMUDbackend architecture
0 likes · 11 min read


21CTONov 4, 2015 · Backend Development
This article traces the evolution of game server architectures from the first MUD systems in 1978 through successive generations—including HTTP‑based card/runner servers, the MUDOS engine, split‑world models, seamless world servers, Battle.net, casual and modern action MMOs—highlighting design choices, scalability challenges, and practical trade‑offs.
BackendMMOMUD
0 likes · 21 min read
