[Django]-Switching from MySQL to Cassandra – Pros/Cons?

by

38👍

✅

Cassandra and the other distributed databases available today do not provide the kind of ad-hoc query support you are used to from sql. This is because you can’t distribute queries with joins performantly, so the emphasis is on denormalization instead.

However, Cassandra 0.6 (beta officially out tomorrow, but you can build from the 0.6 branch yourself if you’re impatient) supports Hadoop map/reduce for analytics, which actually sounds like a good fit for you.

Cassandra provides excellent support for adding new nodes painlessly, even to an initial group of one.

That said, at a few hundred writes/minute you’re going to be fine on mysql for a long, long time. Cassandra is much better at being a key/value store (even better, key/columnfamily) but MySQL is much better at being a relational database. 🙂

There is no django support for Cassandra (or other nosql database) yet. They are talking about doing something for the next version after 1.2, but based on talking to django devs at pycon, nobody is really sure what that will look like yet.

👤jbellis

19👍

If you’re a relational database developer (as I am), I’d suggest/point out:

  • Get some experience working with Cassandra before you commit to its use on a production system… especially if that production system has a hard deadline for completion. Maybe use it as the backend for something unimportant first.
  • It’s proving more challenging than I’d anticipated to do simple things that I take for granted about data manipulation using SQL engines. In particular, indexing data and sorting result sets is non-trivial.
  • Data modelling has proven challenging as well. As a relational database developer you come to the table with a lot of baggage… you need to be willing to learn how to model data very differently.

These things said, I strongly recommend building something in Cassandra. If you’re like me, then doing so will challenge your understanding of data storage and make you rethink a relational-database-fits-all-situations outlook that I didn’t even realize I held.

Some good resources I’ve found include:

👤codemonkey

1👍

The Django-cassandra is an early beta mode. Also Django didn’t made for no-sql databases. The key in Django ORM is based on SQL (Django recommends to use PostgreSQL). If you need to use ONLY no-sql (you can mix sql and no-sql in same app) you need to risky use no-sql ORM (it significantly slower than traditional SQL orm or direct use of No-SQL storage). Or you’ll need to completely full rewrite django ORM. But in this case i can’t presume, why you need Django. Maybe you can use something else, like Tornado?

👤logan

Leave a comment