How can we deploy & connect a database into multiple locations? What advantages and disadvantages will it have? And most importantly, what kind of performance will it provide?

1. CASSANDRA ON
EPAM CLOUD
DATABASE DEPLOYED INTO MULTIPLE LOCATIONS

2. AGENDA
• Motivation
• Solutions with Cassandra
• Cassandra on EPAM Cloud

3. @gitaroktato gitaroktato
https://www.linkedin.com/in/oreszteszgitaroktato
Oresztész Margaritisz
• Lead Software Engineer
• Distributed / Cloud Computing
• NoSQL
• Agile
• DevOps
Hi!

4. MOTIVATION

5. MOTIVATION
• EPAM needs global delivery of services
• 25 countries
• 4 continents
• ~ 22,000 employees

6. USE-CASES
• ~ 1200 companies
• EPAM use-cases
• ~ 6 - 12 nodes in production
• ~ 300 - 3000 TPS for read / write
• ~ 300 - 1024 GB per node

7. SOLUTIONS WITH
CASSANDRA

8. R/W
Client
R/W
Client

9. TokyoMinsk
Client

10. Client

11. CASSANDRA ON EPAM
CLOUD

13. AWS-AP-NORTHEASTEPAM-BY1

14. PERFORMANCE
• Replication latency between regions
• Transactions per second for the whole cluster
• 3 instance in Minsk & Tokyo
• 2 CPU
• 4 GB RAM

15. REPLICATION LATENCY
Client Client
WRITE READ
Client
WRITE
READ
NTP

16. REPLICATION LATENCY
0 50 100 150 200 250 300 350 400
TCP Ping
DC1 -> DC2
Single Client
Average 99% Max

17. 0 5000 10000 15000 20000 25000 30000
LOCAL_QUORUM
Replication: 2
LOCAL_ONE
Replication: 2
LOCAL_ONE
Replication: 1
node #1 node #2 node #3 SUM
THROUGHPUT

20. SUMMARY
• Configuration is easy
• Migrating data between locations is built-in
• Load spread evenly
• Dealing with network failures by default

21. ?