In last week's episode of The Cockroach Hour, Jim Walker chatted with Cockroach Labs PMs Piyush Singh and Tommy Truongchau, along with security lead Aaron Blum, to talk about security features in CockroachDB. The full video is available here, and the transcript is below.

In last week's episode of The Cockroach Hour, Jim Walker chatted with Red Hat principal product manager Scott McCarty to talk about everything from the what the future of serverless and distroless are, to what happens when you run Oracle on Kubernetes. The full video is available here, and the transcript is below.

CockroachDB is a Distributed SQL database. That means for the person doing the querying, everything looks like the SQL they’ve known for years. But under the hood, there’s a lot more going on. In order to achieve the bulletproof resiliency and elastic scalability CockroachDB delivers, data is replicated and geographically distributed across nodes of a cluster, and read and write requests are automatically routed between nodes as appropriate. Replication and geo-distribution mean that your nodes have a shape--a topology--and how you design that topology allows you to make important tradeoffs regarding latency and resilience.

There’s a new paradigm in the database industry: Databases-as-a-Service. With their inherent advantages in elasticity, cost of ownership, and provisioning flexibility, the Database-as-a-Service (DBaaS) model is quickly becoming the easy choice for small companies and startups. But in enterprise environments, navigating a paradigm shift like this is a different story. In enterprise environments, it may be imprudent to break completely from the on-premises past and present. As is always the case, diligent enterprise organizations must survey the market and take a holistic approach that deals with their data needs in totality.

CockroachDB was designed to be the open source database our founders wanted to use. It delivers consistent, scalable SQL in a distributed environment. Developers often have questions about how we've achieved this, and our short answer is this: Distributed SQL. Our long answer requires a deeper understanding of CockroachDB’s unique architecture.

Cockroach Labs is proud to participate in DigitalOcean’s annual Hacktoberfest, a celebration of open source and community innovation. The month-long event encourages everyone from experienced developers to students and code newbies to make positive contributions to an ever-growing community. All backgrounds and skill levels are encouraged to complete the challenge. Once a hacker submits four high-quality pull requests, they receive a custom t-shirt from DigitalOcean.

This post was originally published in 2017, upon announcing that CockroachDB’s support for Hibernate was in beta. Today, we’re excited to announce some big news: the CockroachDB dialect for Hibernate is officially available! 🥳 Hibernate now offers first-class support for CockroachDB. You can read more about the dialect, and our journey to get there, in this blog post.

The first version of CockroachDB Dedicated, our database-as-a-service product, had our users fill out a Google doc with their cloud deployment preferences. We’ve come a long way since that initial proof of concept (including, yes, building a UI). More importantly, we’ve put implementation patterns in place that make something complicated (like configuring a cloud deployment) scalable. As we’ve written about before, choosing to run CockroachDB Dedicated on Kubernetes is a huge part of that implementation pattern.

Databases are evolving. For the past decade, we’ve read thinkpiece after thinkpiece taking firm stances on the “SQL vs. NoSQL” debate--some of which declaratively pronounce the death of SQL or the death of NoSQL. In DZone’s annual report on SQL v NoSQL database usage, we’re excited to see that we’re moving beyond that paradigm. What we’re seeing in this report is more nuanced, and a lot more exciting: the death of the “SQL vs. NoSQL” binary altogether.