3 ms·
Two horrible choices of databases... first they used MongoDB then they migrated to Cassandra. I've used tons of databases [1] in production and those two are th
by welder 5y ago
Two horrible choices of databases... first they used MongoDB then they migrated to Cassandra. I've used tons of databases [1] in production and those two are the worst.
[1] I've used RethinkDB, Postgres, MongoDB, MySQL, Cassandra, CockroachDB, TimescaleDB, SSDB, and others
- kin 5y agoCassandra has been successfully deployed at many companies. Would you care to provide some insight into your experience and why you consider it one of the worst?
- welder 5y agoHere's a bug I ran into a few years ago: https://datastax-oss.atlassian.net/browse/PYTHON-891 https://datastax-oss.atlassian.net/browse/PYTHON-891 With all the issues I encountered using in prod, it gave the impression of an overly complicated key/value store.
- winrid 5y agoWhat would you have chosen?
- welder 5y agoAn in-house data service built with RocksDB/LevelDB. [1] [1] https://rocksdb.org/ https://rocksdb.org/
- anaganisk 5y agoIm not questioning your intellect, but each database has its own use case for usage. You might be expecting wrong things from Mongo or cassandra. Using gazillion databases for wrong use cases doesnt mean nothing. From your child comment, you cooked up an in house solution, it may be best suited for you. But for others it would be horrible too. If Cassandra is suited for Facebook, I think the problem is with you making a choice to use it for something its not suited for rather than the database itself.
- welder 5y agoYes, you're right.