The document discusses the evolution and architecture of online games from subscription-based models to free-to-play systems, highlighting key performance metrics and technological infrastructure. It emphasizes the critical importance of extensive testing and analytics in managing growing transaction volumes and improving user experience. Key challenges identified include write-heavy operations, dependencies on external services, and the necessity of sophisticated developer tools.

1. No
Free
Lunch
Transac/ons
in
Online
Games
James
Gwertzman
(formerly
PopCap/EA)
Chief
evangelist,
Code.org
HPTS
2013

2. Pay
up
front
Free
Mul/player
Singleplayer

3. Top
10
highest
grossing
iPhone
games
Source:
ThinkGaming

4. 1997
2009
2013
2004
• PC-­‐based
MMORPG
• 150-­‐200K
subscribers
• 67K
peak
concurrent
• Custom
servers
• Flat
file
storage
• Data
center
• Minimal
analy/cs
• Subscrip/on
• PC-­‐based
MMORPG
• 12M
subscribers
(2010)
• 1M
peak
concurrent
(7K
per
server)
• Custom
servers
• RDBMS
storage
• Data
center
• Minimal
analy/cs
• Subscrip/on
• Web-­‐based
casual
game
• 80M
monthly
ac/ve
• 30M
daily
ac/ve
• LAMP
stack
servers
• RDBMS
storage
• AWS
cloud
• Heavy
analy/cs
• Free
to
play
• Mobile
casual
game
• 25M
downloads
• ???
daily
ac/ve
• LAMP
stack
servers
• RDBMS
+
NoSQL
• Data
center
• Heavy
analy/cs
• Free
to
play

5. WoW
Architecture
Gaming
Client
Login
Server
Game
Server
Game
Server
Game
Server
Game
Server
Game
Server
Game
Server
Game
Server
Game
Server
Game
Server
Game
Server
Game
Server
Game
Server

10. Main
Database
Read-­‐only
Slave
Read-­‐only
Slave
Read-­‐only
Slave
Game
processing…
Replica/on
Wri/ng
back
data
to
master
DB
Up
to
2
hour
delay

12. Source:
AppAnnie

13. Fixes
Before
A(er
1
database
20
databases
(w/
hash
on
user
ID)
Physical
hardware
Virtual
servers
Single
connec/on
to
shared
ID
system
Mul/ple
VPN’s
into
shared
ID
system
Support
manually
fixing
corrupt
user
data
Fixed
root
cause
of
corrupt
user
data
EA
Central
Services
Central
User
ID
Service
Game
Server
/
Database(s)

15. Source:
AppAnnie

16. Things
they
did
right
• Tes/ng,
tes/ng,
and
more
tes/ng
– Used
AWS
to
set
up
1000’s
of
nodes,
millions
of
users
– Found
problems
w/
concurrent
connec/ons
– Fixes:
OS
level
tuning,
op/mize
network
code,
add
more
hardware,
upgrade
load
balancer
• Shrank
save-­‐game
payload
(30K-­‐>3.5K)
• Architected
right
from
start
– User
data:
shards
– Analy/cs-­‐>Logs-­‐>Hadoop-­‐>Data
Warehouse
(cube)

18. Trends
• Tes/ng
is
HARD
but
CRITICAL
– Scale
=
millions
of
users
– Use
real
“user
stories”
–
end-­‐to-­‐end
cases
– Semng
up
test
(adding
10M
records)
takes
days
• Analy/cs
=
more
and
more
transac/ons
– More
than
half
of
all
transac/ons
now…
– Understand
what’s
going
on
inside
the
game
– Especially
w/
shin
to
free-­‐to-­‐play

19. Summary
of
Challenges
• Writes
>
Reads
• Dependencies
on
external
services
• Transac/ons
growing
faster
than
users
• Unsophis/cated
developers

20. Off-­‐the-­‐shelf
tech
roundup
Web
Server
nginx,
apache
Storage
MySQL,
MongoDB,
zBase
Mul/player
Server
SmartFox,
Photon

21. Ques/ons?
james@playfab.com