Amazon Web Services 클라우드를 사용한 게임 성공 사례!!Younjin Jeong Solutions Architect

Mobile Game Trend

Free to play !

In app purchases !

Cross platform !

Go Global !

User retention = Revenue !

Short Life Cycle

Trends

변동성 심한 수요 대응 필요!!

수익화 모델 중요

다양한 디바이스 지원!!

글로벌 진출 위험 최소화

유저 행태 분석 필요!!

실패에 대한 리스크 최소화

Implications

Success!

$3 billion company, $2.4 million per day

Gaming on AWS

Time

Growth

general success graph

Time

GrowthBefore After

Time

GrowthBefore After

Fail fast, fail cheap

Time to market

Scalability

Extend life cycle

Go globalUncertainty and risk mgmt

Before cloud,

Traditional infrastructure

space for rack power source

peering, bandwidth server engineering

storage operating systems

maintenance !

COMSUMES !

TIME + MONEY

Traditional infrastructure

Edge Locations

Dallas(2)

St.Louis

Miami

JacksonvilleLos Angeles (2)

Palo Alto

Seattle

Ashburn(2)

Newark

New York (2)

Dublin

London(2)

AmsterdamStockholm

Frankfurt(2)

Paris(2)

Singapore(2)

Hong Kong

Tokyo

Sao Paulo

South Bend

San Jose

OsakaMilan

Sydney

On a global footprint

Seoul

Manila

Warshaw

Marseille

Regions

And,

Coming soon! AWS China Region

Time

Growth

Time to market

Scalability

Extend life cycle

Go globalUncertainty and risk mgmt

Fail fast, fail cheap1

http://aws.amazon.com/solutions/case-studies/ubisoft/

10 social games in 18 months

Fail fast, Fail cheap1

Time

Growth

Fail fast, fail cheap Scalability

Extend life cycle

Go globalUncertainty and risk mgmt

Time to market2

http://aws.amazon.com/solutions/case-studies/supercell/

Time to Market2

Time

Growth

Fail fast, fail cheap

Time to market

Scalability

Extend life cycle

Go globalUncertainty and Risk Management

3

http://www.slideshare.net/AmazonWebServices/mbl304

Uncertainty and Risk Management3

Time

Growth

Fail fast, fail cheap

Time to market Extend life cycle

Go globalUncertainty and Risk Management

Scalability4

http://aws.amazon.com/solutions/case-studies/rovio/

http://www.slideshare.net/aoemedia/angrybirds-magento-cloud-deployment

Scalability4

50 Instances

250 Instances

# instances vs. CPU utilization

Auto Scaling Background •평균 CPU 사용량에 따라 Instance의 개수 변경 •주로 저녁 시간 대에 User가 몰리고, 새벽 시간 대에는 감소!Action •유저가 없는 새벽 시간 대에는 50대, Peak 시간 대에는 250 대로 유연하게 운영 !Benefits •기존 대비 비용 절감

Scalability4

Time

Growth

Fail fast, fail cheap

Time to market

Go globalUncertainty and Risk Management

Scalability

Extend life cycle5

Extend life cycle5

Extend life cycle5

Time

Growth

Fail fast, fail cheap

Time to market

Uncertainty and Risk Management

Scalability

Extend life cycle

Go global6

http://www.slideshare.net/AmazonWebServices/halfbrick-keynote

Go global6

Go global6

MMORPG, FPS?

http://www.cmune.com/2010/12/12/amazon-case-study-on-uberstrike-for-real-time-cloud-gaming/

http://www.slideshare.net/AmazonWebServices/gmg203lessons-learned-meteor2012final

http://aws.amazon.com/solutions/case-studies/naughty-dog/

aws.amazon.com