Apache Cassandra vs. SQLite

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Cassandra
Score 9.0 out of 10
N/A
Cassandra is a no-SQL database from Apache.N/A
SQLite
Score 9.6 out of 10
N/A
SQLite is an in-process library that implements a self-contained, serverless, zero-configuration, transactional SQL database engine. The code for SQLite is in the public domain and is thus free for use for any purpose, commercial or private. SQLite is one of the most widely deployed databases in the world.N/A
Pricing
Apache CassandraSQLite
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
CassandraSQLite
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Apache CassandraSQLite
Considered Both Products
Cassandra
Chose Cassandra
It was packaged with the vendor product we bought. Also, it’s good for high performance transactional systems. I'm part of our NoSQL team and Cassandra quickly became a favorite for developers with agile teams.
Chose Cassandra
DynamoDB is good and is also a truly global database as a service on AWS. However, if your organization is not using AWS, then Cassandra will provide a highly scalable and tuneable, consistent database.
Cassandra is also fault-tolerant and good for replication across multiple …
Chose Cassandra
Cassandra has its own use case. It performs very well as a data store. Data can be written to it at a high rate. It cannot be compared to traditional RDBMS like Oracle, because they all have their own usage. Even MongoDB, which is somewhat similar, cannot be stacked up against …
Chose Cassandra
We evaluated MongoDB also, but don't like the single point failure possibility. The HBase coupled us too tightly to the Hadoop world while we prefer more technical flexibility. Also HBase is designed for "cold"/old historical data lake use cases and is not typically used for …
Chose Cassandra
Technology selection should be done based on the need and not based on buzz words in the market (google searching). If your data need flat file approach and more searchable based on index and partition keys, then it's better to go for Cassandra. Cassandra is a better choice …
Chose Cassandra
Cassandra is the only NoSQL database I have extensive experience with. In terms of other open source database solutions, I can say that I like Cassandra as much or equally as traditional Oracle MySql, and a lot more than PostgresSQL. The decision to use Cassandra was driven by …
Chose Cassandra
Against HBASE, writes were faster. Reads not so much. Also ability to store in other formats would be good (such as objects). Compared to aerospike, does not compare. Aerospike blows it out of water.
Chose Cassandra
Cassandra does one thing very well. It's able to collect any type of metrics and analytics and store them at very fast speeds. But when it comes to reading the data, there are minor performance issues. That's when other databases such as couchdb or couchbase come in. They can …
Chose Cassandra

These are the features which makes Cassandra different from others:

  • Cassandra is a distributed datastore, with a built-in coordinator. This means that requests are intelligently forwarded to the correct node.
  • It is generally very fast, and especially shines with write heavy …
Chose Cassandra
Apache Cassandra has the best of both worlds, it is a Java based NoSQL, linearly scalable, best in class tunable performance across different workloads, fault tolerant, distributed, masterless, time series database. We have used both Apache HBase and MongoDB for some use cases …
Chose Cassandra
Four years ago, I needed to choose a web-scale database. Having used relational databases for years (PostgreSQL is my favorite), I needed something that could perform well at scale with no downtime. I considered VoltDB for its in-memory speed, but it's limited in scale. I …
Chose Cassandra
I tried to evaluate Cassandra against Voldemort and found Cassandra more efficient when writing scalable applications.
Chose Cassandra
We also evaluated mySQL and mongoDB. Both of them have their strengths and weaknesses but they are less suited for storing massive amounts of time series data. In addition, they are not elastic by nature and we required a "future-proof" solution as it was difficult to estimate …
Chose Cassandra
Cassandra is well suited to more complex networks like multiple data centers. The underlying distributed systems logic is fundamentally sound.
SQLite
Chose SQLite
I also use other Database Systems, but for small apps with offline storage, SQLite is a good and easy to use Database.
Chose SQLite
SQLite is faster and also Light weight as compared to Microsoft SQL Server. Also being open source it reduces the application development cost drastically
Chose SQLite
SQLite has CRUD queries and manipulates external files. Cross-platform support includes iOS, Android, Mac OS X, and Windows. Compared to other databases, it is fast and straightforward to implement. Even if an application crashes, there is no effect on the database or the data …
Chose SQLite
We looked at other traditional RDBMS products, but found them to be cumbersome to deploy. They take up more space, and consume more computing resources than SQLite does. While the performance or direct integration to our primary applications may have been better or easier if we …
Chose SQLite
SQLite has many types of queries to do CRUD operations. and even do manipulation to external files as well. it is fast and easy to implement compared to other Databases.
SQLite support atomic behaviours, so app crash in any situation, the won't impact database or data within …
Chose SQLite
Microsoft SQLExpress: More heavyweight, not as lean in terms of disk space or processing requirements. Involves Microsoft's tentacles to be involved.
Chose SQLite
SQLite is considered better against these two depending on the needs and phase of the project. If we require a lightweight yet reliable database which should also be portable across different platforms and speed is the most important part of the query and data security is not …
Chose SQLite
I think there is no real competition between them.
In "SQLite" you can hear "light" when you don't need to store a big amount of data and when you need something easy to deploy, SQLite is a good choice, I didn't find those qualities in other database systems I knew.
Chose SQLite
When looking at the original items available, Valentina was a serious contender. What was good about SQLite was the familiar SQL interface and way it accessed data. Valentina, at the time, had issues with index corruption requiring vigilance with the database maintenance making …
Chose SQLite
SQLite stacks quite well against Microsoft SQL server management studio however we need the Microsoft security for our data MDSN documentation is poor but available.
Features
Apache CassandraSQLite
NoSQL Databases
Comparison of NoSQL Databases features of Product A and Product B
Apache Cassandra
8.0
Ratings
10% below category average
SQLite
-
Ratings
Performance8.50 Ratings00 Ratings
Availability8.80 Ratings00 Ratings
Concurrency7.60 Ratings00 Ratings
Security8.00 Ratings00 Ratings
Scalability9.50 Ratings00 Ratings
Data model flexibility6.70 Ratings00 Ratings
Deployment model flexibility7.00 Ratings00 Ratings
Best Alternatives
Apache CassandraSQLite
Small Businesses
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
InfluxDB
InfluxDB
Score 8.8 out of 10
Medium-sized Companies
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
Neo4j
Neo4j
Score 9.8 out of 10
Enterprises
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
Neo4j
Neo4j
Score 9.8 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apache CassandraSQLite
Likelihood to Recommend
6.0
(0 ratings)
10.0
(0 ratings)
Likelihood to Renew
8.6
(0 ratings)
-
(0 ratings)
Usability
7.0
(0 ratings)
9.0
(0 ratings)
Support Rating
7.0
(0 ratings)
1.0
(0 ratings)
Implementation Rating
7.0
(0 ratings)
-
(0 ratings)
Configurability
-
(0 ratings)
10.0
(0 ratings)
Ease of integration
-
(0 ratings)
10.0
(0 ratings)
User Testimonials
Apache CassandraSQLite
Likelihood to Recommend
Cassandra excels in a broad range of applications -- especially if you understand its data model and write your applications accordingly. It's an excellent choice for time-series data, and a poor choice for application queues. It performs the best if you can simply record history and compute from it, rather than going back and editing or deleting things a lot.
Read full review
The portability and ease of use has us doing local development, and then shipping the database to production for implementation. This compact deliverable object is great. Until multiple developers need to access it at a time. It is a caveat, but we create a database per integration as it is easier to manage. Using a SQLite database to manage more than one integration or task is not something we would recommend.
Read full review
Pros
  • High Availability - we utilize the data replication features of Cassandra. This enables us to access our data even when several nodes have gone down
  • Data Locality - our architecture combines Cassandra storage nodes and computation nodes in the same machine. This enables us to utilize data locality and limit expensive network IO to read data.
  • Elasticity - Cassandra is a shared nothing architecture. Nodes can be added very easily and they discover the network topology. As soon as a node has joined the Cassandra ring, the data is redistributed among the existing nodes and streamed to it automatically.
Read full review
  • Our products are using SQLite in embedded Linux and in Windows software.
  • It is truly a stable cross-platform database.
  • The fact that it is a zero-configuration database engine, it is particularly a nice advantage when you work in the embedded world.
  • Being a single database file, it provides ease for those who need to quickly transfer data to someone else, or quickly browse data.
Read full review
Cons
  • No Ad-Hoc Queries: Cassandra data storage layer is basically a key-value storage system. This means that you must "model" your data around the queries you want to surface, rather than around the structure of the data itself.
  • There are no aggregations queries available in Cassandra.
  • Not fit for transactional data.
Read full review
  • Although it is excellent at what it does, you should be really careful and plan accordingly if you know that your database is going to scale at a huge level because it is not suitable of databases which are of Enterprise level and demands top-notch security and protection.
  • If your project involves multiple people working on the same database simultaneously, then that becomes a big problem, because it only allows single write at one time. You really need to be forward thinking in a manner to predict if this database will cater to all the needs of your project.
  • The most common difficulty with this is the lack of some of the basic functionality which is present in the other premier databases like Joints, Stored Procedure calls, Security and permission grants. If you do require all those things then you are better off not using this software.
  • Lastly, if you are using this in an Andriod App development cycle then also your options are limited because it does not integrate with PostgreSQL and MYSQL.
Read full review
Likelihood to Renew
I would recommend Cassandra DB to those who know their use case very well, as well as know how they are going to store and retrieve data. If you need a guarantee in data storage and retrieval, and a DB that can be linearly grown by adding nodes across availability zones and regions, then this is the database you should choose.
Read full review
No answers on this topic
Usability
It’s great tool but it can be complicated when it comes administration and maintenance.
Read full review
I have had a wonderful experience with SQLite because in my every project I use SQLite in the development phase because it's really fast, doesn't crash and very easy to maintain as well. It saves a lot on physical memory and dedicated server usage. It has all the basic functionality you would need to get the job done and that too at no cost at all. What more could you ask for !!!
Read full review
Support Rating
Sometimes instead giving straight answer, we ‘re getting transfered to talk professional service.
Read full review
I haven't needed support yet.
Read full review
Alternatives Considered
Apache Cassandra has the best of both worlds, it is a Java based NoSQL, linearly scalable, best in class
tunable performance across different workloads, fault tolerant, distributed, masterless, time series database. We have used both Apache HBase and MongoDB for some use cases which were within hadoop setup and JSON (JavaScript Object Notation) document store respectively, but given the overall factors favoring Apache Cassandra, it is a technology choice for multiple platforms!
Read full review
SQLite has CRUD queries and manipulates external files. Cross-platform support includes iOS, Android, Mac OS X, and Windows. Compared to other databases, it is fast and straightforward to implement. Even if an application crashes, there is no effect on the database or the data it contains. The user interface is best for input and output. It's best for developing skills and project deliverables.
Read full review
Return on Investment
  • The open source version of Cassandra is only suggested for learning the basic concepts and play with its core features. Unless you really want to invest a lot in your developers and architects knowing every detail of Cassandra, I prefer the DataStax enterprise version. Although the license cost is relatively high, I think they it is worth it. I'm thinking about the support, the monitoring tool OpsCenter, and the integration of Solr and Spark (for data analysis).
  • Cassandra didn't fully replace our old and traditional relation database Oracle. In addition, it opens another door for us to deal with some special business use cases that NoSQL database can do better in a more feasible and efficient way.
Read full review
  • No licensing fees has a net increase on ROI
  • The active community has kept support costs low, further increasing ROI
  • The wide range of supported platforms and high level of compatibility has increased ROI by reducing time spent porting the database model to any platform specific solutions.
Read full review
ScreenShots