Couchbase Server Use Case: Mobile Game Cookierun

김민우 (Minwoo Kim)

minwoo.kim@devsisters.com

2014. 1. 24

Cookierun History• Ovenbreak (2009)

• Ovenbreak2 (2012)

• Cookierun for Kakao (2013 April ~ )

• 16 million downloads

• DAU avg. 2 million

• Google Play Store Game Rank (In S. Korea)

Infrastructure

• Amazon Web Service

• Route53, Auto Scaling, ELB, EC2, S3, CloudFront, RDS, …

• KT IDC, Ucloud

• Game Content Delivery

Software Stack• Game API Server

• Java, Spring MVC, Mybatis

• MySQL 5.5 , Couchbase 2.2.0

• Tomcat 6.0, Ubuntu Linux 13.04

• Game Management System

• Python, Django, Boto (AWS Client)

• Service Monitoring

• CloudWatch, Zabbix, SNS, Statsd + Graphite

• Log Analytics

• Logstash, ElasticSearch, MapReduce(EMR)

Service Architecture

Availability Zone-1 Availability Zone-2

Front-end game service

CloudFront Edge

S3 Buckets CloudFront Download Distribution

EC2 EC2

ELB

RDS

Database group

Mobile Game User

Apple / Google Push Service

EC2

Log Search (real-time)

EC2

Game & Server Monitoring

Auto-scalinggroup

EC2

Chef & Git Conf. Management

Log archives Patches & Game Data

CloudFormation

CloudWatch

Internet

Couchbase Cluster

EC2

Couchbase Instance• AMI Type : Hi1.4xlarge

• CPU Intel Xeon E5-2620(Westmere) 2.4GHz

• RAM 60.5GiB

• SSD 1990GB

Couchbase Statistics

• get 80K / sec

• set 5K / sec

• 3~4 times at peak

Review Couchbase• Just in my personal opinion.

• Pros

• High performance

• Easy to install (through web-based console)

• Easy to scale out (in just a few clicks)

• Powerful web admin console

• Cons

• Not popular in S. Korea. (compared with Redis, …)

• Not enough Korean docs and books

• Not fit every situation (sometimes we need RDB features.)

Thanks• You can get more details by the following slide:

• http://www.slideshare.net/serialxnet/kgc2013-1

• We’re recruiting now.

• Feel free to contact us by apply_dev@devsisters.com