News for hackers. Stuff that matters.
Re:12 Months with MongoDB by jasonjei on Monday October 25, 2010 @07:20PM (#1832075)
I think it's a bit short-sighted to assume everyone can use MongoDB if you're dealing with ACID type apps, or anything that deals with money. It's silly to say that they're developing at a much slower rate than someone that is. Use the right tool, or a combination of right tools, for the job.
Re:12 Months with MongoDB by mathias_10gen on Monday October 25, 2010 @07:54PM (#1832187)
While I don't support a blanket statements along the line of "every app should be using MongoDB," it is equally invalid to say that "anything that deals with money" has no use for MongoDB. If you look at http://www.mongodb.org/display/DOCS/Production+Deployments you will see a few financial and ecommerce sites. I can tell you that there are even more financial firms not on that list in various stages of production. Even if your entire app can't be written using MongoDB, it is still worth investigating if the time savings of using it for a portion outweigh the costs of using an additional data store. But that is more of a business question than a technical one.
Re:12 Months with MongoDB by ergo98 on Monday October 25, 2010 @08:21PM (#1832272)
>you will see a few financial and ecommerce sites

Could you provide some examples? Scanning the list I see a couple that have a very periphery relation to financials, but the actual applications have very little financial applicability (and the implementations are trivial).

Though the person you responded to didn't actually say that `"anything that deals with money" has no use for MongoDB"', so you're setting up a strawman regardless.

Re:12 Months with MongoDB by jasonjei on Monday October 25, 2010 @08:59PM (#1832393)
Thanks, ergo98. I definitely think MongoDB can be used in money applications.

But there's almost always some ACID requirement when you're dealing with accounting, e.g, crediting payment or billing fees.

I would use something that could handle transactional ACID processing in combination with MongoDB depending on the application.

Re:12 Months with MongoDB by mathias_10gen on Monday October 25, 2010 @09:47PM (#1832550)
In that case, I apologize. I have seen people using the same argument to claim that MongoDB is unsuitable for use in ecommerce and assumed you were doing the same.
Re:12 Months with MongoDB by weixiyen on Tuesday October 26, 2010 @03:19PM (#1835612)
> so you're setting up a strawman

I find that ironic.

Re:12 Months with MongoDB by ergo98 on Wednesday October 27, 2010 @04:33PM (#1840334)
That's nice.
Re:12 Months with MongoDB by weixiyen on Monday October 25, 2010 @07:23PM (#1832087)
Yes everyone, upvote the strawman argument.
Re:12 Months with MongoDB by pierrefar on Monday October 25, 2010 @07:26PM (#1832103)
Why is it wrong to upvote the argument that says "use the tool that suits the job"? MongoDB fits some use cases really well, and even then we're still learning how to use it (read the post about the problems they had and how they fixed them). It's basically like any other database: it's good for some things, not so good for others, and when you use, learn it like you would learn any other part of your technology stack.
Re:12 Months with MongoDB by weixiyen on Monday October 25, 2010 @07:33PM (#1832124)
> Why is it wrong to upvote the argument that says "use the tool that suits the job"?

1) Because it's a strawman argument.

2) Because the reply addresses a very small subset of apps, which 10gen specifically says is not recommended for use with MongoDB.

My point is simply that you gain productivity and Mongo tends to get a lot of hate on HN. My time is limited. For 90% of use cases, I am going Mongo.