卡桑德拉牺牲了什么部分CAP定理？为什么？ [英] Which part of the CAP theorem does Cassandra sacrifice and why?

问题描述

这里有一个好消息关于使用 Kingsby的Jesper库模拟Cassandra中的分区问题。

There is a great talk here about simulating partition issues in Cassandra with Kingsby's Jesper library.

我的问题是 - Cassandra主要关注CAP定理的分区部分，还是一致性是你需要管理的一个因素吗？

My question is - with Cassandra are you mainly concerned with the Partitioning part of the CAP theorem, or is Consistency a factor you need to manage as well?

推荐答案

Cassandra通常被归类为AP系统，这意味着可用性和分区容限通常被认为比一致性更重要。然而，现实世界系统很少整齐地归入这些类别，因此将CAP看作是一个连续体更有帮助。大多数系统将做出一些努力以保持一致，可用和分区容忍，并且许多（包括Cassandra）可以根据最重要的事情进行调整。像复制因子和一致性水平这样的旋钮可以对C，A和P产生巨大的影响。

Cassandra is typically classified as an AP system, meaning that availability and partition tolerance are generally considered to be more important than consistency. However, real world systems rarely fall neatly into these categories, so it's more helpful to view CAP as a continuum. Most systems will make some effort to be consistent, available, and partition tolerant, and many (including Cassandra) can be tuned depending on what's most important. Turning knobs like replication factor and consistency level can have a dramatic impact on C, A, and P.

即使定义术语的含义也是具有挑战性的，有不同的要求。因此，不是将系统分类为CP，AP或其他任何内容，它更适用于根据用例调整这些属性的选项。

Even defining what the terms mean can be challenging, as various use cases have different requirements for each. So rather than classify a system as CP, AP, or whatever, it's more helpful to think in terms of the options it provides for tuning these properties as appropriate for the use case.

这是一个有趣的讨论从CAP定理第一次引入以来的事情发生了变化。

Here's an interesting discussion on how things have changed in the years since the CAP theorem was first introduced.

这篇关于卡桑德拉牺牲了什么部分CAP定理？为什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！