1 views collected around this technical thread.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.