May 2017 Summaries
2 posts from Cockroach Labs
Filter
Month:
Year:
Post Summaries
Back to Blog
In the first-ever Cockroach Labs podcast, co-founders Peter Mattis, Spencer Kimball, and Ben Darnell discuss the journey of developing CockroachDB 1.0, an open-source, cloud-native SQL database. They provide insights into the challenges and excitement surrounding the production-ready release, highlighting key features like multi-active availability and production readiness, including zero downtime upgrades and backup capabilities. The founders share personal anecdotes about their early collaborations, technical debates, and aspirations for CockroachDB's future applications. They also reflect on their personal interests, such as favorite inventors, hypothetical technologies, and alternative career paths, while inviting listeners to explore CockroachDB 1.0 and participate in upcoming meetups in San Francisco and New York City.
May 11, 2017
4,714 words in the original blog post.
CockroachDB has announced the release of its first open-source, cloud-native SQL database, CockroachDB 1.0, marking its transition from beta to a production-ready solution designed for diverse business scales. This release introduces distributed SQL capabilities that enhance scalability and reliability, providing fully-distributed ACID transactions and supporting analytics queries through a new distributed query execution engine. The database emphasizes multi-active availability, ensuring strong consistency and high availability without the drawbacks of traditional replication methods. CockroachDB's flexible deployment options allow for seamless integration across various environments, and its self-hosted commercial offering includes features like distributed incremental backup and restore for enterprise-scale operations. The company has also secured a $27 million Series B funding round, led by Redpoint Ventures, to support its growth and development, highlighting the significant interest in its innovative approach to data management. As CockroachDB continues to evolve, it plans to introduce geo-partitioning to optimize data architecture for global services and address challenges related to data sovereignty and latency.
May 10, 2017
1,520 words in the original blog post.