MongoDB 2.6 Released • Hacker News Board

Re: MongoDB 2.6 Released

#71

Post by AdrianRossouw » Tue, Apr 08, 2014, 4:32 PM UTC

arkham wrote: post #48

AdrianRossouw wrote: post #40

So i've been trying to find an the ideal case for mongodb, because I have to teach a nosql database to some people I am mentoring. I'm leaning heavily towards couchdb though. http://daemon.co.za/2014/04/when-is-mongodb-the-right-tool

Well, for teaching purposes, independent of suitability for a use case there are multiple courses available for free here: http://education.mongodb.com And, more node.js specific (but also offline capable, and available any time): http://mongodbschool.io/

thanks.

the latter is especially useful. I'll pass it along to people for extra reference.

Re: MongoDB 2.6 Released

#72

Post by mateo411 » Tue, Apr 08, 2014, 4:34 PM UTC

rdtsc wrote: post #59

outside1234 wrote: post #17

Earlier quoted context omitted.

Everything will segfault under certain circumstances.

Have never seen my python server segfault.

Yes.

Re: MongoDB 2.6 Released

#73

Post by AdrianRossouw » Tue, Apr 08, 2014, 4:38 PM UTC

id wrote: post #47

AdrianRossouw wrote: post #40

So i've been trying to find an the ideal case for mongodb, because I have to teach a nosql database to some people I am mentoring. I'm leaning heavily towards couchdb though. http://daemon.co.za/2014/04/when-is-mongodb-the-right-tool

While MongoDB has many use cases, it's just perfect if you need to pass over JSON to your JavaScript. Or need JSON output for any other reason.

I can't see how that's a defining feature for it, because couchdb and others also do this really really well. Most of the time you don't even need db drivers, because couchdb is just a REST server.

Re: MongoDB 2.6 Released

#74

Post by bpicolo » Tue, Apr 08, 2014, 4:46 PM UTC

Oculus wrote: post #67

The main reason I use MongoDB on Node is the maturity of the Mongoose ORM - I've used Node-ORM 2, BookshelfJS, and SequelizeJS and none of them felt as mature as Mongoose.

Mongoose is definitely a pleasure to work with, regardless of MongoDB faults. Well-designed.

Re: MongoDB 2.6 Released

#75

Post by alayne » Tue, Apr 08, 2014, 4:48 PM UTC

rainmaking wrote: post #60

herge wrote: post #28

Earlier quoted context omitted.

Really? Have you ever tried to search for specific content in structured documents on a filesystem?

You are referring to using an index, correct? Because grep is absolutely, madly efficient for a doing a full search. The index portion of a file system are called files and directories. Several file names can refer to the same data. Those are called hard links. So with hard links, I can refer to a Foo by their related Bar. /foo/foo1 /foo/foo2 /foo/by_bar/bar1 /foo/by_bar/bar2 /foo/by_bar/bar3 /bar/bar1 /bar/bar2 /bar…

Grep is essentially the slowest way to search content. It has to read every byte. You can do much better with term/field indexing.

Why would you be calling grep from an online application anyway?

Re: MongoDB 2.6 Released

#76

Post by zaidf » Tue, Apr 08, 2014, 4:50 PM UTC

id wrote: post #47

AdrianRossouw wrote: post #40

So i've been trying to find an the ideal case for mongodb, because I have to teach a nosql database to some people I am mentoring. I'm leaning heavily towards couchdb though. http://daemon.co.za/2014/04/when-is-mongodb-the-right-tool

While MongoDB has many use cases, it's just perfect if you need to pass over JSON to your JavaScript. Or need JSON output for any other reason.

On the list of reasons to use MongoDB, shouldn't being able to pass over JSON be at the bottom of the list given how trivial it is to pass a mysql row as a json array?

Re: MongoDB 2.6 Released

#77

Post by tbarbugli » Tue, Apr 08, 2014, 4:50 PM UTC

How is it possible to have aggregation cursors without crunching the complete data set in advance (aka map/reduce) and still have consistent and correct results?

Re: MongoDB 2.6 Released

#78

Post by colechristensen » Tue, Apr 08, 2014, 5:00 PM UTC

mason55 wrote: post #68

brokentone wrote: post #51

Can someone with more MongoDB experience give me your thoughts on the upgrade difficulty here? Worth doing soon, or waiting for a point release? Does this require a data rebuild/update process (coming from 2.4)?

IMO unless you desperately need one of the new features I would hold off a few weeks. With a release this big I'd expect there will be some bugs and wouldn't be surprised to see 2.6.1 shortly.

This is always best practice for anything important unless you find your life is dull and bereft of emergency.

Re: MongoDB 2.6 Released

#79

Post by disbelief » Tue, Apr 08, 2014, 5:06 PM UTC

danielrpa wrote: post #8

A lot of hype... And we still have db level locking. If document level is too difficult, at LEAST do collection level (not that it is too much better, but least it some real improvement).

Every Mongo release announcement I hold out hope for an improvement to database-level write lock, and every time I'm disappointing. Considering this is probably the #1 or #2 complaint people have with Mongo, I'm surprised it hasn't been addressed ahead of some of the other features that have made it in to recent releases.

Re: MongoDB 2.6 Released

#80

Post by woah » Tue, Apr 08, 2014, 5:09 PM UTC

Oculus wrote: post #67

The main reason I use MongoDB on Node is the maturity of the Mongoose ORM - I've used Node-ORM 2, BookshelfJS, and SequelizeJS and none of them felt as mature as Mongoose.

Great ORM. Has undoubtedly made MongoDB millions by now.