Hacker News new | past | comments | ask | show | jobs | submit login

Here's one:

You're dealing with a torrent of incoming semi-unstructured data, where losing a good chunk of it is minor nuisance because you only need a decent sample, from which you extract data.

In those kind of scenarios, making it easy to work on the code can often be far more important than reliability.

I have a project like that now. I'd love to use Postgres, and probably will eventually once things "settle down" and we know what data we need to store. But or now MongoDB is the "quick and dirty" solution. We define a schema client side for everything we nail down, so as we nail down more aspects of what data to process, it gets easier to transition to a proper database.

As ORMs get better support for Postgres' JSON capabilities, it will likely get less and less appealing to use MongoDB for stuff like this too.




Ah, yes multiple downvotes without explanation, that always convinces me.


That's a totally valid reason to use Mongo, now if only they'd market themselves that way.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: