January 2024 Summaries
13 posts from Cockroach Labs
Filter
Month:
Year:
Post Summaries
Back to Blog
CockroachDB 23.2 introduces support for both SERIALIZABLE and READ COMMITTED isolation levels, providing guidance for users to select the appropriate transaction isolation level for their applications. SERIALIZABLE, which prevents all isolation anomalies, is the default and highest isolation level, but it results in more transaction retry errors due to its conservative detection of potential interference between transactions. READ COMMITTED, a weaker isolation level, is commonly used in other databases because it minimizes blocking and interference, offering more predictable performance while requiring careful use of explicit locks to prevent data bugs. The choice between these isolation levels significantly impacts application development: lower isolation levels necessitate explicit locking, whereas higher isolation levels may require retry loops in the application code to handle transaction retry errors. The article emphasizes the importance of understanding these practical implications over the specific data anomalies prevented or allowed by each isolation level.
Jan 31, 2024
1,158 words in the original blog post.
CockroachDB v23.2 introduces physical cluster replication (PCR), a feature designed to enhance disaster prevention by replicating data asynchronously at the byte level across two clusters, thus ensuring business continuity without the latency issues associated with cross-region writes. This update addresses limitations faced by enterprises with legacy failover strategies limited to two regions, unlocking the full resilience features of CockroachDB. PCR provides an automated and flexible solution allowing for multiple standby clusters and cloud configurations, offering a more efficient alternative to traditional backup and restore models by maintaining constantly updated replicas, thereby lowering recovery point objectives (RPO) and recovery time objectives (RTO). The feature, currently in preview and requiring an enterprise license, is part of a broader shift towards disaster prevention over recovery, aiming to maintain application availability even amid regional outages.
Jan 29, 2024
838 words in the original blog post.
CockroachDB is designed to be a reliable and high-performing database for global-scale, mission-critical workloads, as evidenced by its use by major companies such as DoorDash and Netflix. To ensure its capabilities, Cockroach Labs conducts extensive stress-testing and benchmarking, including daily, weekly, and pre-release tests using industry-standard benchmarks like TPC-C and TPC-E, as well as custom tests that closely mimic customer workloads. These tests evaluate various performance aspects, including transaction throughput, latency, scalability, and system behavior under typical operations like backup and schema changes. The database's performance is continuously refined through microbenchmarks that detect subtle changes in system components, and Cockroach Labs collaborates with customers to test specific use cases at large scales. Recent tests have explored the database's capacity to handle complex queries, high transaction rates, and significant storage requirements, ensuring functional correctness and identifying areas for optimization.
Jan 25, 2024
1,688 words in the original blog post.
Storj, a startup, is challenging major cloud storage providers by creating a globally distributed, S3-compatible object storage platform that outperforms traditional providers in certain areas. Described by its CTO, Jacob Willoughby, as akin to "AirBnB for data storage," Storj utilizes under-utilized storage drives worldwide to offer cloud storage at significantly lower costs and with a reduced carbon footprint. The platform ensures security and high performance by encrypting data, fragmenting files, and distributing them globally. A key component of Storj's success is its use of CockroachDB, a database that supports its complex, scalable storage system. This partnership has enabled Storj to handle substantial growth and increases in load without disruption, allowing the company to focus on product development rather than database management. Willoughby highlights that Storj's performance remains consistent even over long distances, whereas traditional providers' performance degrades with distance, and anticipates further load increases with confidence in the system's scalability.
Jan 23, 2024
705 words in the original blog post.
The integration of CockroachDB and Confluent presents a powerful combination for businesses seeking efficient and resilient data architectures, leveraging change data capture to enhance real-time analytics and event-driven processes. This collaboration capitalizes on the distributed nature of both systems, ensuring service continuity even when individual nodes encounter failures, while also offering seamless scalability to accommodate growing data demands. As fully managed, cloud-native platforms, CockroachDB Cloud and Confluent Cloud reduce maintenance burdens and operational complexities, allowing companies to focus on innovation without infrastructure worries. Furthermore, their global presence and geo-replication capabilities provide a robust solution for enterprises operating on a global scale. With a pay-as-you-go pricing model, businesses can optimize resource utilization and minimize costs, making this integration an attractive proposition for modern data management needs.
Jan 22, 2024
592 words in the original blog post.
CockroachDB 23.2 introduces a range of new tools and capabilities aimed at enhancing resilience and performance for enterprises facing increasing global data volumes and the need for robust data management. The release includes innovative features like the MOLT Live Migration Service, which facilitates smooth database transitions, enhanced disaster recovery capabilities, and physical cluster replication to improve resilience without latency increases. Additionally, the update supports stored procedures using SQL or PL/pgSQL, read committed isolation for compatibility with high-concurrency Postgres applications, and improved Postgres compatibility with features like entity framework and column-level encryption. These enhancements aim to help organizations modernize their infrastructure, ensuring business continuity and supporting mission-critical workloads with zero downtime, ultimately making it easier to transition from legacy databases.
Jan 18, 2024
1,222 words in the original blog post.
"Big Ideas in App Architecture" is a weekly podcast hosted by David Joy, offering insights from tech industry experts on building modern, data-intensive systems. The podcast covers a range of topics, including Chick-fil-A's use of edge computing to enhance app performance, Andy Pavlo's application of machine learning for database optimization, and Matt Ranney's strategies for improving microservices reliability at DoorDash. Other episodes explore Peter Mattis's journey with CockroachDB, Shadi Rostami's innovative engineering culture at Amplitude, and Ken Pickering's insights into data warehousing. The series also features discussions on maintaining legacy systems with Marianne Bellotti, multi-cloud adoption with Erol Kavas, fostering strong engineering teams with Meg Adams, and Joe Lynch's theories on software engineering practices. Each episode provides valuable technical insights and lessons learned, aiming to help listeners enhance their own system designs and engineering approaches.
Jan 17, 2024
1,431 words in the original blog post.
The text discusses the evolving relationship between SQL databases and cloud technology, highlighting the limitations of traditional SQL databases like MySQL and PostgreSQL when adapted to cloud environments. It contrasts Google Cloud SQL, which offers managed SQL services on Google Cloud Platform, with distributed SQL databases like CockroachDB, which are designed for cloud-native, distributed systems and offer advantages in scalability, availability, and compliance with data regulations. Google Cloud SQL can face challenges such as region-specific availability and scaling limitations, whereas CockroachDB supports multi-region deployments and can scale both reads and writes across nodes. While both systems have their merits, CockroachDB is particularly suited for large-scale, mission-critical applications, while Google Cloud SQL is more appropriate for traditional relational workloads that do not demand extensive scalability or availability. The text suggests that multicloud deployments are becoming increasingly common and important for businesses.
Jan 16, 2024
1,325 words in the original blog post.
The text discusses the advantages of PostgreSQL, a popular open-source relational database, highlighting its strict data type enforcement, extensiveness of data types, and suitability for various applications. It covers various data types such as boolean, character, integer, serial, decimal, time, UUID, JSON, and arrays, explaining their storage capabilities and use cases, especially in distributed systems. The text also introduces CockroachDB, a distributed SQL database compatible with PostgreSQL, which offers features like automated sharding, elastic scaling, and multi-active setup, making it ideal for cloud environments. Additionally, it touches on the ease of migrating from PostgreSQL to CockroachDB due to their compatibility, though some schema adjustments may be needed for optimal performance.
Jan 12, 2024
1,404 words in the original blog post.
A humorous yet insightful anecdote recounts how a simple data entry error in the Job Control Language (JCL) led to the United States Postal Service (USPS) overpaying $500 million to 150,000 employees. This incident occurred due to a JCL operator entering the wrong year, compounded by the unexpected federal holiday following Ronald Reagan's death, which left no one in the finance department to catch the mistake. The USPS payroll, one of the largest and most complex systems globally, was disrupted, causing a massive overdraft and requiring a collaborative effort over the weekend to correct the error. The situation necessitated intervention from the Secretary of the Treasury and took several months to resolve, highlighting the critical nature of detail-oriented work in large-scale systems and the occasional unpredictability of life events intersecting with technology. Remarkably, no one was fired over the incident, and the tale serves as a reminder of the non-technical challenges faced by those in technical roles.
Jan 11, 2024
980 words in the original blog post.
Materialize, an operational data warehouse, achieves sub-second latency by streaming data from various sources in real time, allowing businesses to leverage data instantly. Initially, Materialize operated as a single binary limited to a single node, which restricted its database size and fault tolerance. In 2022, they transitioned to a cloud-based architecture to enhance scalability and availability without compromising speed and correctness. This transition involved adopting managed services such as Amazon EKS and Amazon S3, but they needed a robust metadata layer, leading them to evaluate several database options. They selected CockroachDB for its managed solution, which met their requirements for speed, correctness, and scalability, as well as provided a positive collaborative experience with Cockroach Labs.
Jan 10, 2024
797 words in the original blog post.
Materialize, an operational data warehouse, enhances its speed and correctness by transitioning its high-speed data processing to a cloud-based architecture, leveraging CockroachDB for scalability and managed services. Originally built on open-source frameworks Timely Dataflow and Differential Dataflow, Materialize offers real-time data streaming with sub-second latency, aiming to overcome traditional data warehouses' limitations. To meet its requirements for high availability and rapid query response times, Materialize evaluated several databases, ultimately selecting CockroachDB due to its managed solution and scalability, which aligns with their goal of reducing operational burdens. The collaboration with Cockroach Labs has been fruitful, marked by responsive communication and tailored feature additions, ensuring Materialize's needs are met efficiently.
Jan 10, 2024
754 words in the original blog post.
Shopmonkey, a rapidly growing company in the retail automotive repair industry, faced challenges with data consistency and scaling due to their monolithic application's technical debt. To address this, they re-architected their system using CockroachDB as a managed Database as a Service (DBaaS), enabling highly available and geo-aware database solutions for their widespread user base across North America. This transition required a shift in database design thinking and involved retraining developers to adapt to a distributed mindset. The new architecture includes a setup with three super regions, nine nodes, and custom tools like a connection pooler and a schema change tool named Wrench, ensuring regional consistency and load distribution. CockroachDB's managed service alleviates database operations, allowing Shopmonkey to focus on business-differentiating features, with support available for troubleshooting and optimization.
Jan 03, 2024
713 words in the original blog post.