Photon Real‑Time Networking vs Backend Services: When to Use Which
Photon Engine is synonymous with low‑latency real‑time networking for games, offering engines like Fusion (state synchronization) and Quantum (deterministic simulation). These solve the “netcode” problem—moving game state between players quickly and reliably. However, they are not a complete backend: you still need player authentication, persistent data, leaderboards, economy, and server orchestration. This article explains where Photon fits and when to pair it with a dedicated backend service.
Simple rule: Photon handles the real‑time multiplayer session; a backend service handles everything that persists beyond the session.
What Photon Provides
| Product | Focus | Best For |
|---|---|---|
| Photon Fusion | High‑performance state sync with prediction, lag compensation, and high player counts | Action games (FPS, battle royale) where smooth real‑time movement is critical |
| Photon Quantum | Deterministic simulation with rollback, zero lag, and cheat protection | Competitive games (fighting, sports) that need frame‑perfect consistency |
| Photon Realtime | Low‑level API for rooms, matchmaking, NAT punch‑through, and custom properties | Developers who want to build their own netcode on top of Photon’s transport |
| Photon Chat/Voice | Text and voice communication with 3D audio, noise reduction, and moderation | Social features within multiplayer sessions |
What Photon Does Not Provide
- Player authentication: No built‑in guest‑to‑account flow, OAuth, or JWT issuance.
- Persistent storage: No cloud save, player profiles, or document‑based progression.
- Economy & leaderboards: No virtual currencies, inventory, or ranked seasons.
- Server registry: If you run dedicated servers, Photon doesn’t offer a heartbeat‑based registry or server browser.
- Live config delivery: No over‑the‑air config bundles, feature flags, or environment‑based rollouts.
- Analytics & LiveOps: No player segmentation, A/B testing, or revenue analytics dashboards.
Complementing Photon with a Backend Service
To build a full multiplayer game, you typically combine Photon (networking) with a backend service that handles persistence and operations. Common pairings:
| Backend Service | How It Complements Photon |
|---|---|
| PlayFab | Provides player identity, cloud save, economy, leaderboards, and LiveOps; Photon handles real‑time gameplay. |
| Supercraft GSB | Handles player auth, progression, server registry (if using dedicated servers), and live config; Photon manages the real‑time session. |
| Nakama | Offers social features, storage, and real‑time multiplayer (its own), but can be used alongside Photon for specialized netcode. |
| Custom backend | You build the persistence layer and call Photon’s APIs for matchmaking and room management. |
Architecture Patterns
Peer‑to‑Peer / Hosted Mode
Photon’s default model: one client acts as host, others connect via Photon Cloud. The backend service authenticates players, loads their profiles before joining a room, and records match results afterwards.
Dedicated Game Servers
You run authoritative game servers (using Fusion or Quantum server‑side), and Photon relays or connects clients to those servers. The backend service registers servers, provides live config, and stores player data. Supercraft GSB’s server registry fits here.
Serverless Authority
Use Photon’s “serverless” mode (cloud‑hosted logic) for simple games, but still rely on a backend for persistent data and economy.
When to Choose Photon + Backend Combo
- Your game requires smooth, low‑latency real‑time interaction (shooters, fighters, racing).
- You want a proven networking solution with prediction, lag compensation, and anti‑cheat measures.
- You need persistent player progression, rankings, and inventory that outlive gameplay sessions.
- You plan to run dedicated servers and need a registry, browser, and config delivery.
- Your team prefers to focus on gameplay code while leveraging external services for networking and backend.
When to Consider an All‑in‑One Backend
- Your game is turn‑based or slow‑paced (e.g., strategy, card game) and doesn’t need advanced netcode.
- You want a single vendor for both networking and persistence (e.g., Nakama with its real‑time layer).
- Your budget or complexity tolerance is lower; managing two separate services adds integration work.
- Your game uses a networking engine that already includes backend features (e.g., Metaplay’s shared C# logic).
Integration tip: Authenticate players with your backend first, obtain a session token, then pass that to Photon’s authentication callback. Store match results and player stats in the backend after each session. Use the backend’s live config to tweak game parameters (damage values, drop rates) without patching clients.
Related in This Hub
- Multiplayer Backend Architecture Patterns
- Server Browser & Master Server Design
- PlayFab vs Supercraft GSB Comparison
- Game Server Backend hub
Explore Photon at Photon Engine and backend options like Supercraft GSB.