Nir Shney-Dor of Jelly button games talks about how he uses Redis across many different use cases - as a persistent db, cache, for pub/sub, leaderboards etc etc..Fun walkthrough of all the uses one can put Redis to.

2. ● Jelly Button Games - Introduction
● Pirate Kings - Growth Challenges
● Redis Use Cases
● Summary

5. Spin the wheel to earn cash
and build your island. Attack
and steal from your friends,
But beware they can take
revenge!

7. Pirate Kings

8. ● Soft launch in Israel and Sweden
● Featured in Google Play Asia
● Game grew virally from 100K to 3.5M in 3 months
● 2M Daily Active Users in 10 days
○ 1M requests per minute

9. ● “Always online” players
● Social network with interactions
● Near real-time
○ No lazy dumps

10. Pirate Kings

11. - Our “Swiss Army Knife”
- Using ServiceStack’s Redis client
- Efficient
- Running on RedisLabs

12. ● 100GB DB’s
● Clustered DB’s have 5 shards each (multi-AZ)
● At least 8 CPUs per instance
● Latency: 0.1 msec (avg)
● Network usage: 80k-90k packets/second

13. Redis

14. ● Cache
● Leaderboard
● Persistent DB
● Pub/Sub
● Time Sync

15. ● 13M keys
● 2,500 concurrent connections
● 20K ops/sec
● Average latency of 0.06ms

16. ● A leaderboard is a SortedSet
● Global / Per Country Leaderboard
● Complexity: O(log(n))

17. ● Logging malicious users’ IPs
(INC with TTL)
● Identifying social relations
(Set)
● Cash King super-fast calculation
(SortedSet)
● Beware: Unbounded growth

18. ● Instant player updates
● Configuration changes

19. ● Time syncing issue between
AWS servers
● Used Redis as “Central Time”
● Avoid using as a solution for
time sensitive features

21. ● Jelly Button Games - Introduction
● Pirate Kings - Growth Challenges
● Redis Use Cases

22. Nir Shney-dor
nir@Jellybtn.com