Ogdc 2013 choosing the right database for social mobile game

453 views

Published on

Published in: Technology, Design
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
453
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Ogdc 2013 choosing the right database for social mobile game

  1. 1. Nguyen Thanh Quan Lead System Engineer SO6 - G6 Division
  2. 2. Talk Overview Part II. Decision principles Part III. Choosing the right database Part I. Our story
  3. 3. • G6’s typical social game • Game architecture • Problems • Evolution Part I. Our story
  4. 4. G6’s typical social game
  5. 5. Game architecture • High production quality game • Game logic in client • Can keep a socket Flash Client Side Server Side • Base on a LAMP stack • Game logic in PHP • HTTP connection Web stack
  6. 6. Client Web server #1 Web server #n Web server #2 Game architecture
  7. 7. Game architecture - 50,000 100,000 150,000 200,000 DAUs DAUs
  8. 8. Problems • Memory, hardware has limitation • Not easy for scaling out • 4,000 operation per second • 1,000 write per second • Parsing, locking, loggin g, threads …
  9. 9. Evolution Data is growing rapidly Hardware is not merging as that of data growth Hard to scale using traditional way
  10. 10. Part II. Decision principles High performance High availability High scalability Low in cost Outage stories: zynga, wooga
  11. 11. Part III. Choosing the right database
  12. 12. Pick the right tool for the job
  13. 13. Why NoSQL? High Performance High Scalability Always On Flexible Data Model
  14. 14. NoSQL – Disadvantage • Can’t be use for analytics, reporting … • Lack of relation from one key to another • Packing and un-packing of each key • Need whole value from the key; to read/write any partial information
  15. 15. Comparison • Fast enough • Disk based • 4,000 OPS • 1,000 write/s MySQL • Super fast • RAM based • 50,000 OPS • Writes are fast as reads NoSQL
  16. 16. Game architecture Client Web #1 Web #n Web #2 NoSQL DB Real-time data Analytics data
  17. 17. Our result We reached 1 million DAUs - 500,000 1,000,000 1,500,000 2,000,000 DAUs DAUs
  18. 18. Next stories … and our journey continues…
  19. 19. - 50,000 100,000 150,000 200,000 DAUs DAUs Summarize Evolution everyday
  20. 20. Revolution if necessary Summarize
  21. 21. OPEN GAME DEVELOPMENT CONFERENCE 2013 Nguyen Thanh Quan Lead System Engineer SO6 - G6 Division

×