View all

When you’re hiring for startups, each search for a new teammate can feel like a make-or-break moment for the company’s success. With such great stakes, it’s all the more important to make facts-based, data-driven hiring decisions when interviewing new people. That’s why we’re huge fans of hiring rubrics at Cockroach Labs. Not only do they get us closer to hiring the right person for open roles, they also ensure we have a hiring process that reduces bias. Of course, this is easier said than done. The challenges to developing rubrics mirror their benefits: they require consensus on what it takes to bolster your team’s skills, culture, and diversity.

To help people get outdoors and improve their physical well-being, we’ll create an outdoor activity tracker. Although we won’t cover aspects such as user management, the app will have an input page where users can enter activities such as hiking, skating, swimming, and soccer, with details such as date, duration, distance, and a description. The application’s activities page will list activities from the database and let users sort by fields like date, distance, and duration.

“Do things that don’t scale.” That YCombinator mantra may be the single most common piece of advice given to early-stage tech startups. And with good reason – it’s great advice! But if you follow it, with a little luck you’ll reach a point where it no longer applies (at least on a technical level).

Charlie Custer

February 28, 2022

The concept of a database existed before there were computers. Some of you are even old enough to remember the filing cabinets in which your parents kept health records, tax documents, and old family recipes. The first computer database was built in the 1960s, but the history of databases as we know them, really begins in 1970.

Dan Kelly

February 24, 2022

How can you get great performance out of your database when huge numbers of users are going to be submitting queries within the space of a few minutes or seconds?

Charlie Custer

February 18, 2022

Cockroach Labs has been investing in early career recruiting since we first started the company. In 2016, only a year after the company’s inception, we brought on our first intern. Since then, we’ve steadily built a program driven by a passion for diversity and inclusion, creativity, and unique perspectives.

It’s been three years since this blog was originally published and we’re still feeling great about our decision to prioritize PostgreSQL compatibility. Customers of ours often reference our PostgreSQL compatibility as a reason why the CockroachDB learning curve is so swift. Check out the latest documentation to see the full scope of our compatibility. And then take a look at the original reasons for the decision.

Thanks to services provided by AWS, GCP, and Azure it’s become relatively easy to develop applications that span multiple regions. This is great because slow apps kill businesses. There is one common problem with these applications: they are not supported by multi-region database architecture. CockroachDB is built to solve that problem and we’re doing it in production for many applications today. But that’s not what this blog is about. In this blog, I will provide a solution for the problem of getting Kubernetes pods to talk to each other in multi-region deployments.

The SQL standard defines four isolation levels (READ UNCOMMITTED, READ COMMITTED, REPEATABLE READ, and SERIALIZABLE). SNAPSHOT is a somewhat popular but non-standard addition to this list. People often reach for these words when they want to talk about behavior in CockroachDB in comparison to other databases, even when the behavior in question is not related to isolation.

Ben Darnell

February 11, 2022