Need advice about which tool to choose?Ask the StackShare community!

Cassandra

3.5K
3.5K
+ 1
507
TiDB

73
173
+ 1
22
Add tool

Cassandra vs TiDB: What are the differences?

Introduction

Cassandra and TiDB are both highly scalable distributed databases designed to handle large amounts of data. However, there are several key differences between these two databases.

  1. Consistency Model: Cassandra uses the eventual consistency model, where updates may take some time to propagate across all replicas, allowing for high availability and low latency. On the other hand, TiDB supports both the strong consistency model (ACID transactions) and the eventual consistency model, providing flexibility based on the use case.

  2. Data Model: Cassandra follows a column-based data model, where data is stored in tables with partitions and rows. It can handle structured, semi-structured, and unstructured data. In contrast, TiDB follows a relational data model with tables, columns, and rows, similar to traditional SQL databases like MySQL.

  3. Data Distribution: Cassandra employs a partition-centric model, distributing data across multiple nodes using a consistent hashing algorithm. Each node is responsible for a range of data partitions. In TiDB, data is distributed through a region-based model, where data is divided into regions that can be dynamically scheduled across multiple nodes. This approach allows automatic load balancing and better performance optimization.

  4. Consistency and Availability Trade-off: Cassandra prioritizes availability over consistency, making it well-suited for use cases where high availability and low latency are crucial. TiDB, however, provides a balance between consistency and availability, making it suitable for applications that require strong consistency guarantees.

  5. Scalability: Both Cassandra and TiDB are horizontally scalable databases that support distributed deployments. However, TiDB offers a more straightforward approach to scaling by enabling horizontal scaling of both compute and storage, while Cassandra requires manual tuning and cluster expansion to scale effectively.

  6. Query Processing: Cassandra provides a query language called CQL (Cassandra Query Language), which is similar to SQL but has some differences in syntax and functionality. TiDB supports standard SQL queries and is fully compatible with the MySQL protocol, making it easy to migrate existing MySQL applications to TiDB without any code changes.

In summary, Cassandra and TiDB diverge in their consistency models, data models, data distribution strategies, consistency and availability trade-offs, scalability approaches, and query processing languages. While Cassandra prioritizes availability and eventual consistency, TiDB offers both strong consistency and eventual consistency, making it more versatile for different use cases.

Advice on Cassandra and TiDB
Umair Iftikhar
Technical Architect at ERP Studio · | 3 upvotes · 437.2K views
Needs advice
on
CassandraCassandraDruidDruid
and
TimescaleDBTimescaleDB

Developing a solution that collects Telemetry Data from different devices, nearly 1000 devices minimum and maximum 12000. Each device is sending 2 packets in 1 second. This is time-series data, and this data definition and different reports are saved on PostgreSQL. Like Building information, maintenance records, etc. I want to know about the best solution. This data is required for Math and ML to run different algorithms. Also, data is raw without definitions and information stored in PostgreSQL. Initially, I went with TimescaleDB due to PostgreSQL support, but to increase in sites, I started facing many issues with timescale DB in terms of flexibility of storing data.

My major requirement is also the replication of the database for reporting and different purposes. You may also suggest other options other than Druid and Cassandra. But an open source solution is appreciated.

See more
Replies (1)
Recommends
on
MongoDBMongoDB

Hi Umair, Did you try MongoDB. We are using MongoDB on a production environment and collecting data from devices like your scenario. We have a MongoDB cluster with three replicas. Data from devices are being written to the master node and real-time dashboard UI is using the secondary nodes for read operations. With this setup write operations are not affected by read operations too.

See more
Vinay Mehta
Needs advice
on
CassandraCassandra
and
ScyllaDBScyllaDB

The problem I have is - we need to process & change(update/insert) 55M Data every 2 min and this updated data to be available for Rest API for Filtering / Selection. Response time for Rest API should be less than 1 sec.

The most important factors for me are processing and storing time of 2 min. There need to be 2 views of Data One is for Selection & 2. Changed data.

See more
Replies (4)
Recommends
on
ScyllaDBScyllaDB

Scylla can handle 1M/s events with a simple data model quite easily. The api to query is CQL, we have REST api but that's for control/monitoring

See more
Alex Peake
Recommends
on
CassandraCassandra

Cassandra is quite capable of the task, in a highly available way, given appropriate scaling of the system. Remember that updates are only inserts, and that efficient retrieval is only by key (which can be a complex key). Talking of keys, make sure that the keys are well distributed.

See more
Recommends
on
ScyllaDBScyllaDB

By 55M do you mean 55 million entity changes per 2 minutes? It is relatively high, means almost 460k per second. If I had to choose between Scylla or Cassandra, I would opt for Scylla as it is promising better performance for simple operations. However, maybe it would be worth to consider yet another alternative technology. Take into consideration required consistency, reliability and high availability and you may realize that there are more suitable once. Rest API should not be the main driver, because you can always develop the API yourself, if not supported by given technology.

See more
Pankaj Soni
Chief Technical Officer at Software Joint · | 2 upvotes · 148.8K views
Recommends
on
CassandraCassandra

i love syclla for pet projects however it's license which is based on server model is an issue. thus i recommend cassandra

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Cassandra
Pros of TiDB
  • 119
    Distributed
  • 98
    High performance
  • 81
    High availability
  • 74
    Easy scalability
  • 53
    Replication
  • 26
    Reliable
  • 26
    Multi datacenter deployments
  • 10
    Schema optional
  • 9
    OLTP
  • 8
    Open source
  • 2
    Workload separation (via MDC)
  • 1
    Fast
  • 8
    Open source
  • 6
    Horizontal scalability
  • 4
    Strong ACID
  • 2
    HTAP
  • 1
    Mysql Compatibility
  • 1
    Enterprise Support

Sign up to add or upvote prosMake informed product decisions

Cons of Cassandra
Cons of TiDB
  • 3
    Reliability of replication
  • 1
    Size
  • 1
    Updates
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    What is Cassandra?

    Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.

    What is TiDB?

    Inspired by the design of Google F1, TiDB supports the best features of both traditional RDBMS and NoSQL.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use Cassandra?
    What companies use TiDB?
    See which teams inside your own company are using Cassandra or TiDB.
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Cassandra?
    What tools integrate with TiDB?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    What are some alternatives to Cassandra and TiDB?
    HBase
    Apache HBase is an open-source, distributed, versioned, column-oriented store modeled after Google' Bigtable: A Distributed Storage System for Structured Data by Chang et al. Just as Bigtable leverages the distributed data storage provided by the Google File System, HBase provides Bigtable-like capabilities on top of Apache Hadoop.
    Google Cloud Bigtable
    Google Cloud Bigtable offers you a fast, fully managed, massively scalable NoSQL database service that's ideal for web, mobile, and Internet of Things applications requiring terabytes to petabytes of data. Unlike comparable market offerings, Cloud Bigtable doesn't require you to sacrifice speed, scale, or cost efficiency when your applications grow. Cloud Bigtable has been battle-tested at Google for more than 10 years—it's the database driving major applications such as Google Analytics and Gmail.
    Hadoop
    The Apache Hadoop software library is a framework that allows for the distributed processing of large data sets across clusters of computers using simple programming models. It is designed to scale up from single servers to thousands of machines, each offering local computation and storage.
    Redis
    Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams.
    Couchbase
    Developed as an alternative to traditionally inflexible SQL databases, the Couchbase NoSQL database is built on an open source foundation and architected to help developers solve real-world problems and meet high scalability demands.
    See all alternatives