Developing with mongodb is _lightning fast_ and holds up very very well. If you end up with problems, switch to SQL later!
I don't think a lot of these people hating on the nosql projects have actually tried building something with them.
Developing with mongodb is _lightning fast_ and holds up very very well. If you end up with problems, switch to SQL later!
I don't think a lot of these people hating on the nosql projects have actually tried building something with them.
Most of this is probably having expertise with the tools, but I find that for rapid prototyping the ability to run relational queries is really important, especially since query performance during the prototyping phase isn't really an issue.
Also, no schema means the data structure is more malleable. With the right ORM, this fits in well nicely with polymorphism: I can store objects with some common features in the same collection, but when I retrieve them from the database I get different types of objects which inherit the same base object. mongoengine is one ORM that does this.
Must be nice to have requirements that never change once you've decided on a data representation...
As for changing requirements, mongo handled those well too.
It's certainly not a silver bullet, but when I just need a basic object store the query performance trade-off is worth it.