February 2019 Summaries

The blog post discusses the evolving landscape of data protection laws, highlighting the complexities and challenges businesses face due to varying regulations across countries and even within regions like the European Union. The General Data Protection Regulation (GDPR) is a prominent example, but similar laws are emerging worldwide, including in the United States, where state-specific regulations complicate compliance. Businesses are increasingly concerned about the costs and technical challenges of adhering to these laws, prompting a shift towards global data architectures that can adapt to regional requirements. The post suggests that modern database solutions, such as CockroachDB, offer a way to manage data sovereignty efficiently by allowing data to be partitioned geographically. It concludes on a positive note, emphasizing the benefits of cloud-native, distributed architectures in navigating the complexities of global data protection laws, offering businesses flexibility and scalability in a rapidly changing regulatory environment.

Cockroach Labs has transitioned from semantic versioning to calendar versioning for their release cycle guidelines, moving from version 2.1.5 to 19.1 beta. This change addresses challenges faced under semantic versioning, such as determining significant version jumps without backward-compatible API changes. By adopting calendar versioning, they aim to minimize internal debates, establish clear user expectations regarding release quality and stability, and simplify the understanding of release timelines. Releases will now be named by season and year, with a two-digit year as the major component and release number within the year as the minor one, such as CockroachDB Spring '19. Patch releases will be indicated by a third "micro" number, omitted on the first release number for external representations. The new system is intended to streamline the process and reduce the chance of version-skipping during upgrades.

CockroachDB utilized Jepsen tests nightly to ensure database correctness amidst failures, discovering a post-release bug two years after initial testing. The rigorous testing involved complex environments with network dependencies and cloud VMs, often encountering non-bug-related failures. The bug was identified in a register test with a split nemesis, indicating an inconsistency in the handling of pipelined writes, where a transaction incorrectly signaled completion, leading to resolved intents despite incomplete processes. Despite initial misdirection, the investigation revealed that a simple code fix resolved this significant issue. The endeavor underscored Jepsen's efficacy and limitations as a testing tool, emphasizing the need for more sensitive test workloads to better capture such errors in the future.

The High Availability Architecture Guide compares CockroachDB and Oracle in providing highly available distributed services, emphasizing the trade-off between data correctness and high availability. Oracle, a traditional database designed before the cloud era, requires multiple complex and costly technologies for high availability, often resulting in data anomalies. CockroachDB, however, as a cloud-native database, offers built-in features for always-on availability, strong data consistency, and distributed performance without additional licensing costs. The guide highlights that while Oracle necessitates separate tools and licenses for each high availability feature, CockroachDB includes these capabilities within its database binary, with options for enterprise-grade tools for more complex needs. This comparison aims to clarify the complexity Oracle introduces and suggests that CockroachDB provides a more straightforward, cost-effective solution for high availability architecture.

The 2018 Cloud Report by CockroachDB, a cloud-neutral database, outlines the performance discrepancies observed during tests on major US cloud providers, revealing that AWS clusters achieved 40% higher throughput compared to GCP clusters. This observation prompted further investigation and discussions within the cloud and Cockroach communities, resulting in updates to the report addressing common questions and concerns. The updated report now includes detailed reproduction steps for transparency and audience validation. CockroachDB remains committed to its cloud-neutral stance and plans to expand its benchmarking efforts to include Microsoft Azure and other cloud platforms in future reports, continuously adapting to the evolving infrastructure investments by cloud providers.