Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Don't use MongoDB

pastebin.com

Post reply on HN
Print view View original

301–310 of 331 posts

Re: Don't use MongoDB

#301

Post by megaman821 »

saturn wrote: post #300
nmongo wrote: post #246

Earlier quoted context omitted.

I SUBMITTED THIS STORY AND IT IS IN FACT A HOAX!

What exactly was a hoax? The document pasted was rather detailed and, while somewhat overblown, was obviously written by someone who knew what they were talking about. It contains a lot of criticism of design decisions by MongoDB; these are pretty common and being opinion, can't really be called a hoax. There's also a couple of anecdotes of MongoDB supposedly failing in various ways in the author's experience. Are yo…

This admission has my "spider-sense" tingling also. The communication style between this guy and the author of the pastebin log seems so different.

It is plausible that someone guessed the password of nmongo's throwaway account, quickly changed that password, and then started posting the whole thing was a hoax.

Re: Don't use MongoDB

#302

Post by judofyr »

einhverfr wrote: post #297
betaclass wrote: post #294

Earlier quoted context omitted.

The original story was submitted by nomoremongo, not nmongo. The original story was very detailed and identified known problems with MongoDB. This post is a one-liner. So prove you were the one who wrote the account in pastebin.

A previous discussi ("Failing on Mongo") on had nmongo asking someone to post this with a link to the pastebin.

I think you have it mixed up:

nomoremongo posted the comment at 2011-11-06T03:43:48Z: http://news.ycombinator.com/item?id=3201772

nmongo posted the story at 2011-11-06T07:05:13Z: http://news.ycombinator.com/item?id=3202081

Re: Don't use MongoDB

#303

Post by wizzard »

betaclass wrote: post #294
nmongo wrote: post #246

Earlier quoted context omitted.

I SUBMITTED THIS STORY AND IT IS IN FACT A HOAX!

The original story was submitted by nomoremongo, not nmongo. The original story was very detailed and identified known problems with MongoDB. This post is a one-liner. So prove you were the one who wrote the account in pastebin.

More evidence: nomoremongo and nmongo have some differences in their writing style. nomoremongo uses semicolons properly, nmongo does not. An even bigger difference: nmongo doesn't capitalize his Is.

"Maybe i already work for Fox News"

"and i am the original owner"

"based on the FUD i'm spreading"

"Yes, i am a troll"

"And i think everyone who truly"

It's a different person.

Re: Don't use MongoDB

#304

Post by wedgemartin »

ehwizard wrote: post #138

From CTO of 10gen First, I tried to find any client of ours with a track record like this and have been unsuccessful. I personally have looked at every single customer case that’s every come in (there are about 1600 of them) and cannot match this story to any of them. I am confused as to the origin here, so answers cannot be complete in some cases. Some comments below, but the most important thing I wanted to say is…

We've been using Mongo for almost a year now, and we've not seen any of the major issues such as data loss referred to. We've seen some of the growing pains of a quickly moving, dynamic platform, but nothing outside of the realm of what is reasonable for such a powerful solution. It's true that implementing sharding is no simple task, but with enough planning up front, you'll find yourself able to scale horizontally very quickly. After a couple of weeks of planning, we wound up making a few small changes in our codebase to migrate from master/slave to a sharded environment. Not a huge undertaking by any stretch, provided the current flexibility of our platform. Also, due to the fact that 10gen does make all bug information publicly available, we've managed to get it done with zero surprises.

Wedge Martin CTO Badgeville

Re: Don't use MongoDB

#305

Post by deedubaya »

nmongo wrote: post #246
ehwizard wrote: post #138

From CTO of 10gen First, I tried to find any client of ours with a track record like this and have been unsuccessful. I personally have looked at every single customer case that’s every come in (there are about 1600 of them) and cannot match this story to any of them. I am confused as to the origin here, so answers cannot be complete in some cases. Some comments below, but the most important thing I wanted to say is…

I SUBMITTED THIS STORY AND IT IS IN FACT A HOAX!

Then you are, in fact, a douche.

Re: Don't use MongoDB

#306

Post by phaylon »

einhverfr wrote: post #270
rb2k_ wrote: post #77

Earlier quoted context omitted.

My main problem with schema migrations was that once you reach 100 million records or so, those tend to lock down the DB server and take quite a while

Let's see. On Pg: postgres=CREATE TABLE alter_benchmark(id bigint); CREATE TABLE postgres=# explain analyze postgres-# insert into alter_benchmark (id) select * from generate_series(1, 200000000); postgres=# create temporary table alter_benchmark(id bigint); CREATE TABLE postgres=# explain analyze insert into alter_benchmark (id) select * from generate_series(1, 200000000); QUERY PLAN --------------------------------…

You could try `time psql < alter-statement.sql`. I know, it'd not really be useful as it measures lots of overhead. But if it's fast on that, it's fast during an active session.

Re: Don't use MongoDB

#307

Post by Aaronontheweb »

teyc wrote: post #286
nmongo wrote: post #246

Earlier quoted context omitted.

I SUBMITTED THIS STORY AND IT IS IN FACT A HOAX!

You have too much time on your hands. Hacker News used to be a place where serious and somewhat time poor programmers gather to exchange ideas and learn from one another in good faith . We are certainly not here to listen to some dumbfuck spread misinformation. You should have known better. Consider joining Fox News. But I'm not sure if they'll stoop this low. Kind regards.

Dude, was the Fox News ad hominem necessary? This doesn't look like Reddit...

Re: Don't use MongoDB

#308

Post by christkv »

xxqs wrote: post #127

I wonder why nobody mentions that MongoDB supports x86 CPU architecture ONLY . It keeps unaligned data in its memory structures, and all operations are explicitly little-endian. So, no chance to get it running on any ARM, MIPS, PowerPC or SPARC

There is a fork on github no os86 don't remember the name but is supposed to compile to arm

Re: Don't use MongoDB

#309

Post by harryf »

nmongo wrote: post #246
ehwizard wrote: post #138

From CTO of 10gen First, I tried to find any client of ours with a track record like this and have been unsuccessful. I personally have looked at every single customer case that’s every come in (there are about 1600 of them) and cannot match this story to any of them. I am confused as to the origin here, so answers cannot be complete in some cases. Some comments below, but the most important thing I wanted to say is…

I SUBMITTED THIS STORY AND IT IS IN FACT A HOAX!

Have you ever heard of Gartners hype cycle? http://en.m.wikipedia.org/wiki/Hype_cycle

Hype, fud, fact and misinformation are all part of determining which technologies succeed and which fail.

Many of HN readers have been through 2 or 3 of those cycles and have well developed instincts for spotting BS and verifying technologies.

In other world all you've really demonstrated here is you're a bit of a dick.

Re: Don't use MongoDB

#310

Post by tastynachos »

nomoremongo wrote: post #154

Pastebin author here. Refutations are going to fall into two categories, it seems: 1. Questioning my honesty 2. Questioning my competence Re #1, I'm not sure what you imagine my incentive to lie might be. I honestly just intended this to benefit the community, nothing more. I'm genuinely troubled that it might cause some problems for 10gen, b/c, again, Eliot & co are nice people. Re #2, all I can do is attempt to rea…

I'm going to guess you come from the ops world, I suspect most dev's using mongo aren't really deeply knowledgeable about the things you point out. Sure you know what replication is, but its different once you actually configure it and are tasked to maintain it.

We've been using Mongo in production since 1.6, and I can say I've encountered a lot of things you described in your original pastebin. I'll say it, the product is crap. I've spent more sleepless nights working on mongo than I have with anything else.

Post reply on HN