The document discusses using a key-value store (KVS) to store pageview data more efficiently than a relational database. It proposes storing each pageview record as a key-value pair with the key containing fields like page, gender, age. This allows for fast retrieval of records by key. It also questions whether using MongoDB or another NoSQL database would be better than building a custom KVS on top of MySQL. Finally it provides a link to Gree's career page for additional information.

1. ( )
2012/01/26 (thu) at 2012 #1
/
ichii@gree.co.jp / @ichii386
Thursday, January 26, 12

2. •
• 13F
• 7
•
• MySQL, Solaris, ZFS, InfiniBand
•
•
• perl,
Thursday, January 26, 12

3. •
DB
FILE KVS
hadoop?
•
• pageview
•
• phpmyadmin SQL
Thursday, January 26, 12

4. •
pv.page=foo.gender=female.age=20
• “foo” 20 pv
• iPhone
• web
• :1 x 7
• ID
•
• pv? pageview?
•
Thursday, January 26, 12

5. ?
• KVS
• key
pv {
• key
page: “foo”;
• gender: “female”;
age: 20;
• }
• hash O(1)
• mongoDB ?
• ... !
Thursday, January 26, 12

6. •
3776
• “key= , value=3776 ”
Thursday, January 26, 12

7. (2)
• : WolframAlpha
•
Thursday, January 26, 12

8. • key serialize
• key string CREATE TABLE kvs (
date DATE,
• key KVS key VARCHAR,
val DECIMAL,
• key string UNIQUE KEY (date, key, val),
FULLTEXT KEY (key)
• SVC ) ENGINE=mroonga;
pv.page=foo.gender=female.age=20
•
•
• false positive
• “ key KVS”
Thursday, January 26, 12

9. • (key string )
• RDB schema
• schema less
•
• schema : pageview
• key key
• MySQL JOIN !
• MySQL
Thursday, January 26, 12

10. • key KVS
•
•
•
•
•
•
• MySQL mongo hadoop
•
Thursday, January 26, 12

11. :
• http://gree.co.jp/recruit/
Thursday, January 26, 12