What does multi-cloud look like in the real world? @CockroachDB gathered insights from 300 architects across the US and Europe to answer some of your biggest questions.

Hard Rock Digital's database engineer James Lupolt recently sat down with us to discuss the common challenges of sports betting application architectures and why they chose #CockroachDB.

Cloud concentration risk: The probability of having all of your assets in one specific cloud provider My colleague Dan Holt shared his thoughts on how this issue can impact financial institutions & what potential solutions look like with @DIGIWORLD_INFO

This is a really compelling conversation between my colleague Tim Veil talked and @mranney, Principal Engineer at @Doordash.

Need to scale out? If you're using a distributed SQL database like @CockroachDB, scaling is as easy as adding a new node. If you're using a legacy database, the process is unfortunately far more painful...

“Migrating away from legacy infrastructure isn’t without risk, but the greater risk is of inaction.” Considering moving to a next-generation database? Our CMO Peter Guagenti shared his thoughts on what you should know for @stackpublishing

How do you calculate the total cost of a cloud database? It's a complicated answer, so here's a framework to think about the costs incurred when buying a database.

From co-founding @GIMP_Official to working at @Google to building @CockroachDB, our Co-Founder & CTO @PeterMattis has a fascinating history. Give this episode a listen to learn about Peter and to go under the hood of #CockroachDB.

Should your company be scaling up or scaling out? There is no one-size-fits-all solution, so read on for a closer look at vertical and horizontal scaling, how they compare, and what the pros and cons are for each approach.

Multi-cloud deployments can minimize latency and increase availability. Here's a quick look at why more companies are making the migration and how to deploy your own multi-cloud database.

What if you didn’t have to choose between innovating and reducing costs? And what if you could do so by switching to data management tools that are significantly easier to live with? This free report will show you how it's possible.

Scaling can be one of the biggest challenges for a payments database. Thankfully, #CockroachDB can make this process painless.

During #RoachFest22, we asked some of our customers including @Netflix, @DevSisters, @Shipt, and @Authzed, “What do you think of the name @CockroachDB?” 😮

“This is the first time I’ve been excited about a database. Right out of the box, @CockroachDB solves a lot of challenges for us as a national sportsbook.” - Mick Giles, SVP & Head of Technology at @HardRockDigital

With CDC transformations in CockroachDB 22.2, total cost of ownership (TCO) and time-to-value for some applications can be significantly reduced with little effort. Here's a closer look:

When appointment booking service @BooksyApp needed to take a cloud-first approach, they partnered with @googlecloud and @CockroachDB to make it happen.

When people ask us, “Why did you name it @CockroachDB?” we say, “...because it’s the database you can’t kill…” and the heads nod.

#RoachFest23, our annual @CockroachDB customer conference returns to NYC this October!

The world's top banks are leaving the legacy systems that have powered their workloads for, in some cases, decades. Here's why.

“What @CockroachDB has given us is the ability to meet each state’s regulatory environments à la carte…No matter which states we launch or how many nodes or clusters we add, it is still just one database."