Expertise 05 / Backend & Server Systems

Enough backend depth to own the whole online game

My primary specialization remains Unity/C# game architecture, but I have designed and built the services, data flow, orchestration, and scaling decisions needed to keep client and server one coherent product.

01 / Scope

Services that serve
the game architecture

Metagame services

Player profiles, persistence, matchmaking, commands, responses, HTTP communication, offline behavior, and reconnect.

Battle infrastructure

Battle-server communication, process supervision, server orchestration, deployment topology, failure behavior, and scaling decisions.

Technology selection

Choose established infrastructure that fits the team's skills, operational environment, and growth needs instead of building a platform the product does not need.

02 / Evidence

Server-side work
from implementation to direction

D.A.W.Studio / CTO

Metagame, matchmaking, and battle servers

  • Designed communication across ASP.NET Core metagame services and UDP battle servers.
  • Built a player-profile service and matchmaker backed by MongoDB and Redis.
  • Designed battle-server orchestration and owned backend scaling decisions.
  • Built a Python supervisor that managed processes on battle-server machines; the surrounding service stack was .NET.
  • Supported offline operation and seamless reconnect for both metagame and battle flow.

GoGames / World of Fishing

Hands-on C# server development

  • Led system architecture and implemented the game server in C#.
  • Defined the client/server communication protocol and supported the Flash client.
  • Led the data migration from SQL to MongoDB and Redis.
  • The resulting data-stack experience carried into later work at West-Games and D.A.W.Studio.

Serious Cake / Age of Phoenix

Akka.NET-backed 4X strategy

The game's backend used an actor-based architecture built on Akka.NET.

  • Studied the architecture and contributed selected backend features.
  • Retained primary responsibility for the Unity client.
  • Used the experience later when evaluating distributed-system options for other teams.

Alfa Bravo / Continuing collaboration

Scale without a dedicated backend department

After the employment period, periodic collaboration continued across architecture, technical art, and reusable packages.

  • Recommended Microsoft Orleans for an Azure-based product that needed horizontal scaling and rebalancing.
  • The choice allowed universal developers and the CTO to cover server work without creating a separate backend team.
  • The recommendation prioritized an established platform with built-in capabilities over custom infrastructure.

Wargaming / REVOLT

Server command resolution tied to game rules

Extended a client-architecture rescue into client/server logic and a universal command-processing flow. Players submitted simultaneous-turn actions independently; the server resolved the outcome using unit priority, buffs, and debuffs, and both clients replayed the same authoritative result. This is representative of how I connect backend behavior to the actual game model instead of treating the server as generic transport.

03 / Decisions

Build what is specific
Adopt what is already solved

I am comfortable owning the boundary between game client, shared rules, battle simulation, metagame services, data, and deployment. At the same time, I avoid inventing infrastructure where mature tools provide scaling, recovery, and operational behavior more reliably.

  • Use the product's game model to define commands, state, and failure semantics.
  • Keep online and offline paths coherent rather than maintaining two unrelated applications.
  • Choose databases for the actual access model; later game work favored MongoDB and Redis over the earlier SQL stack.
  • Keep dedicated server processes supervised and failure boundaries explicit.
  • Select distributed frameworks based on team capacity and deployment environment, not novelty.

04 / Relevant stack

Backend and infrastructure