Jepsen Disputes MongoDB's Data Consistency Claims

Re:Jepsen Disputes MongoDB's Data Consistency Claims by vosper on Sunday May 24, 2020 @05:36AM (#23290369)

My claim isn’t that indexes are a bad idea. The comment I replied to suggested that Mongo’s marketing targets people who don’t want to learn how to use indexes; my claim is that the reality of the hosted product is that it frequently suggests that you add indexes (presumably doing so helps with Mongo Corps hosting margins, as well as with performance [which is laughable even with indexes])

[ Parent | on HN ]

Re:Jepsen Disputes MongoDB's Data Consistency Claims by squeaky-clean on Sunday May 24, 2020 @06:27AM (#23290565)

> my claim is that the reality of the hosted product is that it frequently suggests that you add indexes

But it auto-suggests what index to use and has a button for you to immediately apply it. I'd say it definitely intends for you to avoid learning how indexes in MongoDB work. The index suggestions it makes are often terrible.

> performance [which is laughable even with indexes]

It really depends on your use-case and how you can structure and query your data. For one such service I'm the lead on I haven't found anything faster that doesn't sacrifice the ability to do more generic queries when we occasionally need to. (Yes we've benchmarked against postgres json fields which is always everyone's first suggestion)

[ Parent | on HN ]

Re:Jepsen Disputes MongoDB's Data Consistency Claims by vosper on Tuesday May 26, 2020 @07:32PM (#23317676)

> But it auto-suggests what index to use and has a button for you to immediately apply it. I'd say it definitely intends for you to avoid learning how indexes in MongoDB work. The index suggestions it makes are often terrible.

Heh, yeah, you're right. So I guess it's the worst of both worlds: they try to not have you learn about indexes, but they give you terrible index suggestions, so when those don't work out you still end up having to learn about indexes :)

[ Parent | on HN ]