How to reduce TCO while meeting strict regulatory requirements
summary
Hard Rock Digital runs one logical CockroachDB cluster with nodes in EC2 and on AWS Outposts across seven states, cutting duplicated state-by-state stacks and materially lowering TCO while meeting data residency rules. Operational lessons: monitor packet loss (they use SmokePing), prefer isolating flaky links, and colocate some processing to reduce latency. Query wins come from follower reads + non‑voting replicas to avoid leaseholder round trips. Result: single deployable platform, faster market entry, and lower ops overhead.
AI-written summary · about
chapters (12)
- 0:00Welcome/Introduction
- 0:40A quick introduction to Hard Rock Digital
- 1:12Hard Rock Digital's Use Case
- 2:25Regulatory constraints for real-money gaming applications (The Federal Wire Act)
- 3:02How CockroachDB and AWS helped them solve their compliance problem
- 5:04The AWS Cloud Continuum
- 5:55Leveraging AWS Outposts
- 6:37How customer data and processing can stay resident on AWS Outposts
- 7:11Decentralization: Lessons learned
- 8:32Network monitoring: Lessons learned
- 10:22Query performance: Lessons learned
- 12:22Conclusion (Accelerating time to market, write once / deploy anywhere, IaC for operational efficiency)
related talks
29mHow City Storage Systems designed its Data Infrastructure to minimize toil
31mFuture-proofing operational data at scale
48mBuilding mission-critical applications with CockroachDB
14mHow CockroachDB can enable Multi-Region Deployments and Data Locality 
32mHave a SQL and Eat it Too!
15mScaling to support America’s #1 sportsbook
23mRun Less Software; Use Less Bits
27mHow Devsisters launches blockbuster games in new countries with ease