Jepsen Disputes MongoDB's Data Consistency Claims

Post by gav » Sat, May 23, 2020, 9:54 PM UTC

1123581321 wrote: post #70

thomascgalvin wrote: post #53

You can tell a lot about a developer by their preferred database. * Mongo: I like things easy, even if easy is dangerous. I probably write Javascript exclusively * MySQL: I don't like to rock the boat, and MySQL is available everywhere * PostgreSQL: I'm not afraid of the command line * H2: My company can't afford a database admin, so I embedded the database in our application (I have actually done this) * SQLite: I'm…

As someone who chose MySQL and provides direction to developers who really like Postgres, and who also uses Postgres for fun, I do find myself having to both defend MySQL as a prudent option and convince them that I know anything at all about Postgres or computer science. :)

Post by karatestomp » Sat, May 23, 2020, 10:00 PM UTC

collyw wrote: post #87

senko wrote: post #12

Earlier quoted context omitted.

Some readers might not be familiar with that particular meme: https://m.youtube.com/watch?v=b2F-DItXtZs IMHO it perfectly describes the hype-reality disconnect at the early days of MongoDB. Yeah it was that bad. Mongo has improved since, the hype has toned down and the NoSQL space is more crowded these days.

The damage is done. I have to use this crap at work when we should be using an SQL database. We have been planning a migration since before I started a year and a half ago. I won't be surprised if we are still on Mongo in another year and a half.

Post by [deleted] » Sat, May 23, 2020, 10:02 PM UTC

gopalv wrote: post #100

henryfjordan wrote: post #94

Earlier quoted context omitted.

RabbitMQ stores your data, right? Then it's a database! That's pretty much all it takes. A flat file, memory-store, SQL DB, Document store, any of them can be databases if that's where you stick your data! But also no, RabbitMQ and Kafka and the like are clearly message buses and though they might also technically qualify as a DB it would be a poor descriptor.

> Kafka and the like are clearly message buses and though they might also technically qualify as a DB ksqldb is actually a database on top of this. The thing is that they have an incrementally updated materialized view that is the table, while the event stream is similar to a WAL ("ahead of write logs?" in this case). Because eventually you can't just go over your entire history for every query.

Post by cyral » Sat, May 23, 2020, 10:04 PM UTC

VWWHFSfQ wrote: post #99

ForHackernews wrote: post #83

Earlier quoted context omitted.

I've heard MySQL (well, MariaDB, really) has improved a lot in recent years, but I still can't imagine why I'd ever choose it over Postgres for a professional project. Is there any reason? It used to be that bargain basement shared-hosting providers would only give you a LAMP stack, so it was MySQL or nothing. But if you're on RDS, Postgres every time for my money.

mysql's admin tools are still far superior than what's available for postgres

Post by benibela » Sat, May 23, 2020, 10:10 PM UTC

thomascgalvin wrote: post #53

You can tell a lot about a developer by their preferred database. * Mongo: I like things easy, even if easy is dangerous. I probably write Javascript exclusively * MySQL: I don't like to rock the boat, and MySQL is available everywhere * PostgreSQL: I'm not afraid of the command line * H2: My company can't afford a database admin, so I embedded the database in our application (I have actually done this) * SQLite: I'm…