book

Getting Started with CockroachDB

by Kishen Das Kondabagilu Rajanna

March 2022

Intermediate to advanced

246 pages

4h 36m

English

Packt Publishing

Read now

Unlock full access

ContributorsAbout the authorAbout the reviewers
Who this book is forWhat this book coversTo get the most out of this bookDownload the example code filesDownload the color imagesConventions usedGet in touchShare Your Thoughts
The history and evolution of databasesSQLObject-oriented databases NoSQLNewSQLDatabase concepts CardinalityOverview of database modelsProcessing modelsEmbedded and mobile databasesDatabase storage enginesCAP theoremConsistency and partition tolerance (CP)Availability and partition tolerance (AP)Consistency and availability (CA)CockroachDBWhy yet another database?InspirationKey terms and conceptsHigh-level overviewSummary
Technical requirementsInstalling a single-node CockroachDB cluster using DockerExecution of a SQL querySQL query executionParsing Logical planningPhysical planningQuery execution Managing a transactional key-value storeData distribution across multiple nodesThe MSKVSMeta ranges Table dataData replication for resilience and availabilityWhat is consensus? The Raft distributed consensus protocolInteractions with the disk for data storageStorage engine Summary
An overview of ACID propertiesAtomicity Consistency Isolation Durability ACID from CockroachDB's perspectiveAtomicity Consistency IsolationDurability Summary
Technical requirementsIntroduction to geo-partitioning Cloud, regions, and zonesRegionZone Regions and zones on various cloud providersGeo-partitioning in CockroachDBSingle region Multi-region Summary
Technical requirements Achieving fault tolerance Achieving fault tolerance at the storage layerWorking example of fault tolerance at playAutomatic rebalancing Recovering from multi-node failures Summary
Technical requirementsIntroduction to indexesDifferent types of indexesPrimary indexesSecondary indexes Hash-sharded indexesDuplicate indexesInverted indexes Partial indexesSpatial indexesTable joins and indexesBest practices while using indexes Summary

Technical requirementsDDLCREATE ALTER DROPDMLDQLSupported data typesColumn-level constraints Table joinsUsing sequencesManaging schema changesSummary
Technical requirementsIntroducing the admin UICluster overview Metrics deep dive Database and table definitionsUnderstanding sessions Transactions Tracking jobsSummary
Technical requirements Introduction to security conceptsClient and node authenticationGenerating certificates and keys Client authentication Node authenticationAuthorization mechanismsRoles PrivilegesData encryption at rest and in flightEncryption at restEncryption in flightAudit logging RTO and RPOKeeping the network secureSecurity best practicesSummary
Technical requirements Collecting debug logsLog files Log levels Log channels Emitting logs to an external sinkGathering Cockroach debug logs Connection issuesTracking slow queriesCapacity planningConfiguration issuesGuidelines to avoid issues during an upgradeNetwork latencyAdvanced debugging optionsSummary
Technical requirements Performance – Things to consider Infrastructure Popular benchmark suites Benchmarking your specific use casesPerformance benchmarking for CockroachDBMigration – Things to consider Migrating from traditional databasesMigrating from PostgreSQL to CockroachDBSummary
Other Books You May EnjoyPackt is searching for authors like youShare Your Thoughts

Content preview from Getting Started with CockroachDB

Chapter 3: Atomicity, Consistency, Isolation, and Durability (ACID)

In the Chapter 2, How Does CockroachDB Work Internally, we learned about the different layers of CockroachDB. In this chapter, we will learn about what ACID is, its importance, and what the ACID guarantees that CockroachDB provides are.

ACID guarantees the following things:

Atomicity: This is achieved through the notion of a transaction, in which all the statements within a transaction are executed as a single unit. So, either all of them succeed or fail together.
Consistency: The database state should be consistent before and after a transaction is executed and should ensure that the database constraints are never violated.
Isolation: Multiple transactions can get executed ...