Cassandra聽vs聽Elasticsearch

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

Cassandra

3.6K
3.5K
+ 1
507
Elasticsearch

34.2K
26.6K
+ 1
1.6K
Add tool

Cassandra vs Elasticsearch: What are the differences?

Key Differences between Cassandra and Elasticsearch

Cassandra and Elasticsearch are two popular database technologies that serve different purposes in the realm of data storage and retrieval. Here are the key differences between these two:

  1. Data Model: Cassandra is a wide-column NoSQL database that follows a key-value data model. It allows efficient storage and retrieval of vast amounts of data and provides high availability and fault tolerance. Elasticsearch, on the other hand, is a schema-less search engine that stores data in the form of JSON documents and is primarily designed for fast text search and analytics.

  2. Querying Capabilities: Cassandra offers a limited query language, known as CQL (Cassandra Query Language), which supports basic querying functionalities but does not provide full-text search capabilities. Elasticsearch, being a search engine, provides powerful full-text search capabilities out of the box. It supports complex search queries, filtering, aggregation, and relevance scoring, making it suitable for applications that require advanced search capabilities.

  3. Scalability: Cassandra is known for its ability to scale horizontally across multiple machines or nodes, allowing it to handle large amounts of data and high write throughput. It distributes data across the cluster using a partitioning strategy. On the other hand, Elasticsearch also provides horizontal scalability by distributing data across multiple nodes, but it excels in real-time search use cases by utilizing sharding and data replication techniques to achieve high availability and fast search performance.

  4. Data Durability: Cassandra guarantees data durability by providing tunable consistency levels and multi-datacenter replication. It ensures that data is persisted even in the event of node failures. Elasticsearch, by default, provides near real-time search capabilities but does not guarantee the same level of data durability as Cassandra. It focuses more on fast retrieval and indexing of data rather than strict data durability.

  5. Indexing and Document-Oriented Approach: Cassandra does not have a concept of indexing specific fields within a table. It indexes data based on the primary key and can efficiently retrieve data using the primary key or secondary indexes. Elasticsearch, on the other hand, heavily relies on indexing for fast search operations. It automatically indexes all the fields in a document and provides powerful text analysis, tokenization, and full-text search capabilities.

  6. Consistency Model: Cassandra offers tunable consistency, allowing developers to choose between strong consistency and eventual consistency depending on their application requirements. It provides the flexibility to balance consistency, availability, and partition tolerance. Elasticsearch, on the other hand, follows an eventually consistent model where data changes are distributed across the cluster asynchronously, prioritizing search performance over consistency.

In Summary, Cassandra is a highly scalable wide-column NoSQL database designed for high write throughput and fault tolerance, while Elasticsearch is a search engine optimized for full-text search and real-time analytics with powerful querying capabilities.

Advice on Cassandra and Elasticsearch
Rana Usman Shahid
Chief Technology Officer at TechAvanza | 6 upvotes 路 377.7K views
Needs advice
on
AlgoliaAlgoliaElasticsearchElasticsearch
and
FirebaseFirebase

Hey everybody! (1) I am developing an android application. I have data of around 3 million record (less than a TB). I want to save that data in the cloud. Which company provides the best cloud database services that would suit my scenario? It should be secured, long term useable, and provide better services. I decided to use Firebase Realtime database. Should I stick with Firebase or are there any other companies that provide a better service?

(2) I have the functionality of searching data in my app. Same data (less than a TB). Which search solution should I use in this case? I found Elasticsearch and Algolia search. It should be secure and fast. If any other company provides better services than these, please feel free to suggest them.

Thank you!

See more
Replies (2)
Josh Dzielak
Co-Founder & CTO at Orbit | 8 upvotes 路 281.7K views
Recommends
on
AlgoliaAlgolia

Hi Rana, good question! From my Firebase experience, 3 million records is not too big at all, as long as the cost is within reason for you. With Firebase you will be able to access the data from anywhere, including an android app, and implement fine-grained security with JSON rules. The real-time-ness works perfectly. As a fully managed database, Firebase really takes care of everything. The only thing to watch out for is if you need complex query patterns - Firestore (also in the Firebase family) can be a better fit there.

To answer question 2: the right answer will depend on what's most important to you. Algolia is like Firebase is that it is fully-managed, very easy to set up, and has great SDKs for Android. Algolia is really a full-stack search solution in this case, and it is easy to connect with your Firebase data. Bear in mind that Algolia does cost money, so you'll want to make sure the cost is okay for you, but you will save a lot of engineering time and never have to worry about scale. The search-as-you-type performance with Algolia is flawless, as that is a primary aspect of its design. Elasticsearch can store tons of data and has all the flexibility, is hosted for cheap by many cloud services, and has many users. If you haven't done a lot with search before, the learning curve is higher than Algolia for getting the results ranked properly, and there is another learning curve if you want to do the DevOps part yourself. Both are very good platforms for search, Algolia shines when buliding your app is the most important and you don't want to spend many engineering hours, Elasticsearch shines when you have a lot of data and don't mind learning how to run and optimize it.

See more
Mike Endale
Recommends
on
Cloud FirestoreCloud Firestore

Rana - we use Cloud Firestore at our startup. It handles many million records without any issues. It provides you the same set of features that the Firebase Realtime Database provides on top of the indexing and security trims. The only thing to watch out for is to make sure your Cloud Functions have proper exception handling and there are no infinite loop in the code. This will be too costly if not caught quickly.

For search; Algolia is a great option, but cost is a real consideration. Indexing large number of records can be cost prohibitive for most projects. Elasticsearch is a solid alternative, but requires a little additional work to configure and maintain if you want to self-host.

Hope this helps.

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 路 152.4K 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 Elasticsearch
  • 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
  • 328
    Powerful api
  • 315
    Great search engine
  • 231
    Open source
  • 214
    Restful
  • 200
    Near real-time search
  • 98
    Free
  • 85
    Search everything
  • 54
    Easy to get started
  • 45
    Analytics
  • 26
    Distributed
  • 6
    Fast search
  • 5
    More than a search engine
  • 4
    Great docs
  • 4
    Awesome, great tool
  • 3
    Highly Available
  • 3
    Easy to scale
  • 2
    Potato
  • 2
    Document Store
  • 2
    Great customer support
  • 2
    Intuitive API
  • 2
    Nosql DB
  • 2
    Great piece of software
  • 2
    Reliable
  • 2
    Fast
  • 2
    Easy setup
  • 1
    Open
  • 1
    Easy to get hot data
  • 1
    Github
  • 1
    Elaticsearch
  • 1
    Actively developing
  • 1
    Responsive maintainers on GitHub
  • 1
    Ecosystem
  • 1
    Not stable
  • 1
    Scalability
  • 0
    Community

Sign up to add or upvote prosMake informed product decisions

Cons of Cassandra
Cons of Elasticsearch
  • 3
    Reliability of replication
  • 1
    Size
  • 1
    Updates
  • 7
    Resource hungry
  • 6
    Diffecult to get started
  • 5
    Expensive
  • 4
    Hard to keep stable at large scale

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

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 Elasticsearch?

Elasticsearch is a distributed, RESTful search and analytics engine capable of storing data and searching it in near real time. Elasticsearch, Kibana, Beats and Logstash are the Elastic Stack (sometimes called the ELK Stack).

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

Jobs that mention Cassandra and Elasticsearch as a desired skillset
What companies use Cassandra?
What companies use Elasticsearch?
See which teams inside your own company are using Cassandra or Elasticsearch.
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 Elasticsearch?

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

Blog Posts

What are some alternatives to Cassandra and Elasticsearch?
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鈥攊t'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