> their sys admins are dropping Cassandra and pushing all the engineers back to MySql
I'm curious what you are thinking of, because I have better picture of companies using Cassandra than most. :)
I do know of one company that fits your description, where some of the mysql DBAs were very anti-cassandra because, frankly, it's not mysql and that's what they were used to. But that has been resolved (the most vocal DBA left) and the Cassandra migration is continuing.
> If there were any pitfalls or hairy parts with maintain Cassandra, that would be good to know
I'm curious what you are thinking of, because I have better picture of companies using Cassandra than most. :)
I do know of one company that fits your description, where some of the mysql DBAs were very anti-cassandra because, frankly, it's not mysql and that's what they were used to. But that has been resolved (the most vocal DBA left) and the Cassandra migration is continuing.
> If there were any pitfalls or hairy parts with maintain Cassandra, that would be good to know
Other than the obvious (it's not a relational database), we've documented the main limitations here: http://wiki.apache.org/cassandra/CassandraLimitations