Comparing Traditional and Serverless Architectures for a Mobile Multiplayer Game

The article, translated from Mike Roberts and John Chapin’s book What Is Serverless , introduces Serverless concepts and then asks how to compose service components into a complete application, especially for a multi‑user mobile game.

Traditional Non‑Serverless Architecture

The conventional design consists of a native iOS/Android client, a Java application server (running on Tomcat or JBoss) handling business logic, and a relational database such as MySQL storing game state. The mobile client makes HTTP calls to the backend, which manages user authentication, game logic, and persistence.

While functional, this architecture requires expertise in mobile development, Java server management, database administration, and extensive operational effort (configuring hosts, networking, routing, security, scaling, and high‑availability). These complexities become obstacles when fixing bugs, adding features, or iterating quickly.

Why Change?

The traditional stack introduces high labor costs, operational risk, and resource over‑provisioning, making it hard to achieve rapid innovation and cost efficiency.

Serverless Architecture

Serverless replaces the Java server and relational DB with managed services: BaaS (e.g., AWS Cognito for user management) and FaaS (e.g., AWS Lambda functions). API Gateway securely routes HTTP requests from the mobile client to Lambda functions, while a NoSQL store such as DynamoDB holds game state. The client can also access the database directly for leaderboards.

This design dramatically reduces the amount of custom code, eliminates server‑level maintenance, and decouples components, allowing rapid swapping or addition of new logic.

Benefits of Serverless

1. Lower Labor Cost : No need to manage OS patches, database versions, or server infrastructure; BaaS services handle authentication, email, etc., with minimal code.

2. Reduced Risk : Fewer managed components mean fewer failure points; reliance on provider expertise (e.g., DynamoDB) improves reliability and recovery speed.

3. Lower Resource Cost : Pay‑as‑you‑go pricing charges only for actual compute time and storage, avoiding over‑provisioned servers.

4. Improved Scalability : Serverless platforms automatically scale horizontally without manual configuration; Lambda launches containers on demand based on event volume.

5. Shorter Delivery Cycle : Developers can focus on business logic, delivering features in days rather than months, accelerating innovation.

Quotes from industry leaders (e.g., Comcast CTO Sree Kotay and AWS VP Adrian Cockcroft) reinforce that Serverless shortens development cycles, reduces operational overhead, and enables rapid, high‑quality product delivery.

In summary, moving from a traditional architecture to a Serverless model lowers cost, risk, and resource waste while boosting scalability and speed to market for mobile games.