What is the difference between cassandra and mysql

Cassandra is a key-value store like a hashmap that lets you look up plain or structured values based on a key. It does not use fixed predefined tables, but uses a "column-based" model, where each row of data can contain data items of various types, which don't have to be predefined.

Cassandra also provides an older binary query interface via the Thrift protocol. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 10 years, 6 months ago. Active 4 years, 8 months ago.

Viewed 8k times. Hopefully, this would give you the knowledge to choose the right database according to your needs. Here we have discussed Cassandra vs MySQL head to head comparison, key difference along with infographics and comparison table respectively.

You can also go through our other suggested articles to learn more—. Submit Next Question. By signing up, you agree to our Terms of Use and Privacy Policy. Forgot Password? This website or its third-party tools use cookies, which are necessary to its functioning and required to achieve the purposes illustrated in the cookie policy. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to our Privacy Policy.

Popular Course in this category. Course Price View Course. Free Data Science Course. Login details for this Free course will be emailed to you. Email ID. Contact No. JOINS discouraged with the query-driven model.

In these two databases, the information will be stored differently. In Cassandra, you can store the data in a single table. The comments for each user is stored in the form of a list as one single row. In MySQL, you have to make two tables with one-to-many relationships between them.

As MySQL does not permit unstructured data such as a List or a Map, one-to-many relationships are required among these tables. It will require just one lookup. If you have to update a record with an existing primary key,. Cassandra leverages an append-only model. If you want to insert a row that comes with the same primary key as an existing row, the row will be replaced. Or, if you update a row with a non-existent primary key, Cassandra will create the row. Cassandra is very fast and stores large swathes of data on commodity hardware without compromising the read efficiency in any way.

Cassandra can achieve consistency if data duplication is not allowed. Cassandra excels in a wide variety of applications, especially if you know the model of its data and write your applications accordingly. Your question regards 'Relational or not' is obviously key, and you need to consider both your required data structure, as well as the ACID requirements of your application model, as well as the non-functional requirements in terms of scalability, resilience, whether you want security authorisation at the highest application tier, or right down to 'row' level in the database, etc.

Also critical in all this is how many items you believe you need to index by. FIrstly, it may help if you explain what you mean by "complex relationships between project entities". Secondly, you can build a fast and scalable solution using either. I think, Its depend of your project type and your skills.

If you work on little project, use MySQL. I am going to work on a real estate project and have to decide on a database.

Now, SQL databases can be very efficient if appropriately designed. More relations between the data and less redundancy. But with a NoSQL database, the development time is reduced, and it is easy to query.

Since this is my first time working on the real estate domain, I would like to pick a database that would be efficient in the long run. Stay away from foreign keys, keep it fast and simple. Define your data structures well in advance.

This will help you avoid drastic changes to your database after your system is launched. Populate the database with fake data and run tests. PostgreSQL allows you to create Views from multiple tables. Try to create those views and make sure you can easily create useful views from multiple tables. Run an Explain on those view queries to make sure you created your indexes correctly. Any of those three databases are going to be efficient, scalable, and reliable in the long term if you configure and use them correctly.

They all also have solid hosting solutions. All things being equal, I would agree with other posters that Postgres is my preference among the three, but there are caveats. Azure recently bought Citus Data, which was a best-in-class Postgres replication solution, so they might be the only one I trust to provide cross-region replication at the moment. It's a very good implementation and extremely performant. That really depends of where do you see you application in the long run.

On any application, any of those choices are excellent. On the long run, when your application gets hundreds of thousands of requests per second, you might start thinking about how many inputs you will have in the database compared to the outputs.

I'll second another piece of advice. Postgresql's JSON columns are a dream when it comes to productivity and I use them frequently with our Rails application. In these cases, no migration is required to change schema.

We store payloads with dozens or hundreds of keys and performance has not been an issue. We also have a lot of relational tables, so the joins we get with SQL are very important to us and hard to replicate with a NoQL solution. Can someone help me with the version to select?. I have a strong inclination towards MySql 5. But, I see there are some standout features added in Mysql 8. Just wanted to know if the newer version has not compromised on its speed while giving out some add on features.

MySQL 8. For all InnoDB row operations, you'll see a great performance improvement. Also, the time taken to process transactions is lower in MySQL 8. I am trying to design an online ordering app similar to Doordash or Uber Eats. I'm having a hard time trying to finalise on what database or mixture of databases to use.

But, when the application grows, I don't want to join on 20 tables to get a data. Any help would be greatly appreciated. Thank you for your time. Hello Suhas , We build our product www. When using MySQL, i would recommend doing the following: 1. Use Mysql only for storage only and for realtime updates we recommend MongoDB.

Don't try to Join more than 3 tables. Never or very rarely use Auto-increments. Use Node. Let me know if you still need any suggestion's. MySQL is recommended to be used for business logic. PostgreSQL is not recommended since you will be faced with inefficient database replication features and constant migration from one PostgreSQL version to another.

Which database is more secure? Are there others I should be considering? Is it possible to change the encryption keys dynamically? Overall, whatever you choose, the important is to keep it updated and have the skills to apply security best practices and update them regurarly, without this, it's like putting your money in Fort knox but leaving the vault key in a public place.

It is open-source and more tools than mySQL.