This document summarizes Fiserv's use of Redis and conflict-free replicated databases (CRDBs). Fiserv uses Redis for caching, as a primary database, and in cloud infrastructure. They implement CRDBs across data centers in different regions to provide high availability and disaster recovery. The document outlines Fiserv's CRDB infrastructure with clusters in Georgia and Texas, how data flows between the clusters using synchers, and methods for testing the CRDB syncs such as timestamps and network monitoring.

1. PRESENTED BY

2. PRESENTED BY
1 Introduction
Who Fiserv is, and how we use Redis
2 CRDBs From a Fiserv Infrastructure Perspective
How Fiserv uses Geo-replication
3 Conclusion
Summary, and questionnaire
Agenda:

3. PRESENTED BY
Introduction

4. PRESENTED BY
Who is Fiserv?
• Fiserv is a global leader in Financial services Since 1984
– Specialize in Payments, Processing Services, Risk & Compliance, Customer & Channel
management, and Financial Insights and Optimization
– Approx. 12,000 clients in more than 80 Countries
– Fortune 500 for the past 8 years
– 24,000 Employees worldwide
– 5.82 Billion in Revenue for 2018
– More Info:
https://www.fiserv.com/about.aspx
http://fortune.com/fortune500/fiserv/
Introduction

5. PRESENTED BY
How Redis Works for Us?
• Redis Use Cases at Fiserv
– Primary Database
• Redis Open Source
• Redis Enterprise
– Cloud Infrastructure
• Pivotal Cloud Foundry Integration
– Caching
• Session State
– Use Case
– Current State and Future State
– Pain Points (Pre – why Session State in Redis and current problems with an non-geo distributed DB)
Introduction

6. PRESENTED BY
• What is a CRDB?
– Conflict-free Replicated Database
– Active-Active
• Why CRDBs?
– No manual data sync
• Requirements:
– Network
– DNS
– Hardware
• Fiserv Deployment:
– Challenges
– Monitoring
CRDBs with CRDT

7. PRESENTED BY
Fiserv CRDB Infrastructure

8. PRESENTED BY
Fiserv CRDB Infrastructure
GEORGIA TEXAS
App Instance BApp Instance A
Primary Purpose: Current State and Future State (Disaster Recovery)

9. PRESENTED BY
Fiserv CRDB Infrastructure
Creating CRDBs

10. PRESENTED BY
Fiserv CRDB Infrastructure
Creating CRDBs Continued:
• Example:
crdb-cli crdb create --name mycrdb --memory-size 20m --port 15000 --shards-count 1
--instance fqdn=cluster1.demo-rlec.redislabs.com,username=jake@redislabs.com,password=redislabs
--instance fqdn=cluster2.demo-rlec.redislabs.com,username=jake@redislabs.com,password=redislabs
• crdb-cli crdb create
 Options:
–--name
–--memory-size
–--port
–--shard count
–--instance fqdn

11. PRESENTED BY
CRDB Data Flow
Application A -> Cluster 1 CRDB endpoint -> Cluster 2 Syncher -> Cluster 2 CRDB endpoint
Application B -> Cluster 2 CRDB endpoint -> Cluster 1 Syncher -> Cluster 1 CRDB endpoint
Fiserv CRDB Infrastructure
GEORGIA TEXAS
App Instance BApp Instance A
Cluster 1 Cluster 2

12. PRESENTED BY
CRDB Data Flow
• Syncher
• Process that monitors changes on each CRDB
• Runs on one cluster, and establishes a connection to an endpoint on the other cluster.
• To verify running in Linux, use netstat:
Fiserv CRDB Infrastructure

13. PRESENTED BY
Conclusion

14. PRESENTED BY
Summary & Questions
Testing CRDB Syncs
• Time Stamp data entry from application.
• Application Logs, etc.
• In Linux, use Time Command.
• Network Capture on database endpoint of second cluster.
• Hardware network Capture on interface
• In Linux, use tcpdump:
• tcpdump -w crdbdump-w2-2.pcap -s0 -A -vvv -i eth0 port <CRDB endpoint port#>
• Questions?
• Twitter - @Cadet_J3
More Info:
https://redislabs.com/?s=crdt

15. Thank you!
Thank you!