cockroach/docs/design.md at master · cockroachdb/cockroach
CockroachDB is a distributed SQL database. The primary design goals are scalability, strong consistency and survivability (hence the name). CockroachDB aims to tolerate disk, machine, rack, and even datacenter failures with minimal latency disruption and no manual intervention. CockroachDB nodes are symmetric; a design goal is homogeneous deployment (one binary) with minimal configuration and no r
Sorting in Cassandra
The Cassandra distributed data store is, at heart, a key/value storage system. Unlike pure key/value storage systems, however, Cassandra implements first-class notions of key and column ordering. Dominic Williams covered a good chunk of the topic wonderfully in his post “Cassandra: RandomPartitioner vs OrderPreservingPartitioner”. But his framing of the question is a bit different than mine and wa
What is Apache Cassandra? | Open Source Database | DataStax
Cassandra 4.1 is here! Learn more about the most contributor-friendly, easiest-to-run open-source Cassandra to date. Learn More Want to run open-source Cassandra with peace of mind? Learn about DataStax Luna, enterprise support for Apache Cassandra. Learn More Apache Cassandra is a distributed NoSQL database created at Facebook and later released as an open-source project in July 2008. Cassandra d
SSTable
SSTable is an abbreviation for Sorted String Table. It is the fundamental storage building block in few of the modern Log Structured Merge Tree(LSM) based distributed database systems and key-value stores. It is used in Cassandra, BigTable and other systems. SSTable stands for Sorted Strings Table which stores a set of immutable row fragments or partitions in sorted order based on row/partition ke
Using Merkle trees to detect inconsistencies in data
Cassandra's AntiEntropy service uses Merkle trees to detect the inconsistencies in data between replicas. Merkle tree is a hash tree where leaves contain hashes of individual data blocks and parent nodes contain hashes of their respective children. It provides an efficient way to find differences in data blocks stored on replicas and reduces the amount of data transferred to compare the data block
Whats the difference between Paxos and W+R>=N in Cassandra?
Yes, Paxos provides guarantees that are not provided by the Dynamo-like systems and their read-write quorums. The difference is how failures are handled and what happens during a write. After a successful write, both kind of systems behave similarly. The data will be saved and available for reading afterwards (until overwritten or deleted) and so on. The difference appears during a write and after
Cassandra 2.0 に CAS が入るとか入らないとか - kuenishi's blog
CASSANDRA-5062でCAS (Compare and Swap) を入れようという話になっているらしく、一体どんなすごいアトミックブロードキャストを使うのか気になっていた。どういうことなのだろうとスレッドをナナメ読みしてみたのだが…議論の流れとしては カウンターだけじゃなくてCASほしいよねAPIとして ZooKeeperのロック使うのがシンプルでいんじゃね？ いやいやサーバーの種類増やすとかあり得ないし 基本方針は、コーディネーターみたいなのをレプリカセット毎に決めてそこから Chain Replication ぽく コーディネーターどうやって決める やっぱPaxosじゃね？ 再実装ヤダよZAB使おうよZKの実装あるよ （なんかプロトコル上の理由があって）やっぱPaxos実装するしかないか… となって、結局 Jonathan Ellis が Paxos を素で実装してしまった模
Why Cassandra Doesn’t Need Vector Clocks | Datastax
One of the notable features of Amazon's 2007 Dynamo paper was the use of vector clocks for conflict resolution. However, the two most prominent systems designed by engineers who worked on Dynamo -- Cassandra and DynamoDB -- both avoid the use of vector clocks in favor of finer-grained updates. To understand why, let's first look at the problem that vector clocks solve. Resolving conflicts with vec
Cassandra at Scale: The Problem with Secondary Indexes | Pantheon.io
Maybe you’re a seasoned Cassandra veteran, or maybe you’re someone who’s stepping out into the world of NoSQL for the first time—and Cassandra is your first step. Maybe you’re well versed in the problems that secondary indexes pose, or maybe you’re looking for best practices before you invest too much time and effort into including Cassandra in your stack. The truth is, if you’re using Cassandra o
Cassandra Data Modeling Best Practices, Part 1
This is the first in a series of posts on Cassandra data modeling, implementation, operations, and related practices that guide our Cassandra utilization at eBay. Some of these best practices we’ve learned from public forums, many are new to us, and a few still are arguable and could benefit from further experience. September 2014 Update: Readers should note that this article describes data modeli
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Data Locality w/ Cassandra : How to Scan the Local Token Range of a Table... - DZone
Initializing a multiple node cluster (multiple data centers)
Ippon | Cabinet de conseil et expertise en technologie
Lightweight transactions in Cassandra 2.0 | Datastax
Transactions - MongoDB Manual v7.0
About Indexes in Cassandra — Apache Cassandra 1.1.x documentation
Cassandra File System Design | Datastax
第1回 Apache Cassandraを始めよう
Understanding the architecture
DataStax Academy | DataStax
