Hacker News Reader

Comment by xellisx | Hacker News Reader

I had hopes for MongoDB back 10 years ago, but it just let me down.

I'm thinking of trying out ArangoDB next. OrientDB is just riddled with bug and their docs are lack luster.

Why not pick a mature database software, learn to use it properly, and just get on with life? Why would you risk _anything_ to immature databases?d

Exactly. What is the super secret use case that a DB that might shut down in 3 years give you, over the tried and true?

Postgres is great, mysql works... You really need to exhaust them before you go to random.db.

For S&Gs.

It's a 9 year old database.

Can you be more specific about what makes it immature ?

9 years _is_ immature when you're talking about systems that will store data and operate for decades, with various components being upgraded over that time.

Compared to some other databases out there, MongoDB is a baby. These others... are not even born.

Pretty sure that they were referring to ArangoDB and OrientDB as being immature, not MongoDB...

I only migrated companies away from it. I prefer reliable data stores. Postgres + Riak always got my back, 15years, 8 years in production respectively.

Isn't riak dead?

Why would it be?

Because Basho, the company that developed it, is dead?

https://www.theregister.co.uk/2017/07/31/end_of_the_road_for...

Basho was bought and Riak is being developed by the new owner.

I was under the impression that it's no longer being developed.

Even if it was not it would be still good for a KV store.

Do you believe that a software can be complete at all?

It ain't a new cool Javascript library. Databases are hard. Many tried, many failed. Don't play around.

But MongoDB is only 9 yo!

I guess so. I wrote some tutorials back in 2010 https://web.archive.org/web/20100604100310/http://www.dealta...

https://web.archive.org/web/20100725142105/http://www.dealta...

I'd suggest to try the latest FoundationDB MongoDB layer.

I would definitely do that if I had a use case.

Does it offer relationships handling? That's the big downfall of MongoDB for me.

Mongo offers outer left joins through $lookup, now even with sub-queries.

https://docs.mongodb.com/manual/reference/operator/aggregati...

It also offers recursive left outer joins with $graphLookup.

I would have to take a look at that to see if resolves the issues I saw from back then.

There are no explicit foreign key relationships though if that is what you mean ?

I know there was a way to "link" records, but do to do anything with them, you had to pull all the data back into your app and manually filter and process records.

That's not been true for awhile. You use the aggregation framework with the $lookup stage to do an outer left join.

db.employees.aggregate([{ $lookup: { from: "departments", localField: "departmentName", foreignField: "departmentName", as: "managers" } }]);

You can do nested joins as well. However deeply nested joins in MongoDB is probably an anti-pattern.

Reply on news.ycombinator.com