Is it too late to share our New Year’s resolution? (Be the most resilient database in the world, with no downtime and always-on availability.)
Latest & Greatest
Under agentic load, what breaks first?
As AI infrastructure scales, backend systems become the real bottleneck, as legacy databases weren’t built for the demands and scale of AI, breaking often under high volume. Our CEO & Co-Founder Spencer Kimball goes live on January 27, in conversation with Technical Evangelist Rob Reid to share his vision for the AI-native database future, why legacy databases break under agentic workloads, and what AI-ready data architecture means.
The EU Data Act focuses on interoperability, mandating that cloud vendors make it easy for customers to exit their environment when needed. We’re glad to see Google Cloud taking the lead with their Data Transfer Essentials announcement, which introduces no-cost, multicloud data transfers for EU and UK customers.
The business impact: Enterprises can use CockroachDB running on Google’s Compute Engine (GCE) or GKE (Google’s Kubernetes Engine) and sync it to another cloud provider, without incurring data transfer costs.
For mission-critical applications where data loss and downtime must be minimized to seconds, Physical Cluster Replication (PCR) offers a near-synchronous replication of your entire cluster to a standby location.
This "warm standby" approach provides a significantly lower RPO, typically in the tens of seconds, and a much faster RTO, as failing over to the standby cluster is a quicker process than a full restore.
How America’s #1 sportsbook scaled their financial ledger to 13M users
FanDuel serves over 13M active players across 28 states where sports betting is legalized, and 5 states where they are allowed to operate their online casino. To comply with The Wire Act, they must run a ledger and a database(s) in each state they do business. This means their deployment spans across 28 sites and each site has up to three deployment locations. Take a look at an example of what the cluster looks like using three different sites within one locality…and why they placed their bet on distributed SQL!
