1. Riak & Wooga
by Guillermo Álvarez
@guillermooo

2. Wooga

7. API
Key Value Store
+ extras

8. Security
Auth

12. Sinatra

13. Chef + Amazon

14. Riak

16. eLevelDB
5 nodes x m1.xlarge
15 GB, 2 cores, 2 units

17. Ring Size
1024

18. Benchmark
5 MDAU = 225K rpm

21. ( CPU )

23. HA/PROXY
APP SERVERS
RIAK + MEMCACHED

24. MEMCACHED
95% PUTS
5% GETS
99% HITS

25. Benchmark
Again

27. Launch week
Now

31. Monitoring

34. Alerting

36. Problems we
have

37. Riak Ring Size

38. OOM cluster
death

39. 1 Node dies
0 people realize

40. Summary
● You should take care with your ring size
● You must do monitoring
● Reliable

41. Riak for
Pearl’s Peril
Daniel Doubleday
http://de.linkedin.com/pub/daniel-doubleday/1/115/195/

42. Pearl Who?

43. Architecture
Riak 1
Riak n
App
Server 1
HAProxy
App
Server n
HAProxy
Load
Balancer
1
Load
Balancer
n

44. Data Model
User stored as one JSON-CLOB
✘ Every client request needs to read / write
average 4k data
✘ Needs concurrency control
✔ Ensures data consistency
✔ Reduces round trips
✔ Reduces number of keys

45. Data Set
Total : ~ 15M
Keys
New : ~ 50k /
Day
Updates : ~ 100M / Day
Requests : 100 - 200k rpm
Per Server : ~ 75k rpm
RW-Ratio : 50% / 50%

46. Cluster Info
Hardware
Bare Metal, 32GB
6 x 8-core AMD Opteron 2.6GHz
2 x 12-core Intel Xeon 2.0GHz
Riak
Version : 1.3.2
Storage : Bitcask

47. Storage Backend
Bitcask
● Higher Throughput
● Predictable Read
and Write
Performance
LevelDB
● Compression
● Supports large
number of keys

48. The Good

49. A Typical Day

50. Adding a Node

51. The Bad

52. Performance Degradation

53. Nodes doing … things

54. The Ugly

55. Cluster Failures

56. Conclusions
● It works ...
● … most of the time
● NoSQL is becoming commodity
● There’s no shame in using mysql