This week's book giveaways are in the Java EE and JavaScript forums.
We're giving away four copies each of The Java EE 7 Tutorial Volume 1 or Volume 2(winners choice) and jQuery UI in Action and have the authors on-line!
See this thread and this one for details.
The moose likes MongoDB and the fly likes Where to use MongoDB : is it good for structured data Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Databases » MongoDB
Bookmark "Where to use MongoDB : is it good for structured data " Watch "Where to use MongoDB : is it good for structured data " New topic
Author

Where to use MongoDB : is it good for structured data

Kripal Gupta
Greenhorn

Joined: Oct 27, 2010
Posts: 4
I am interested in clear direction on places where it can be applied or has been applied. is it good for structured data or rdms is still the way to go.
Thanks
Rick Copeland
author
Greenhorn

Joined: Apr 09, 2013
Posts: 17
    
    5
Well, that's a pretty open-ended question, which is probably why the answers you've gotten so far have been unsatisfactory.

In general terms, yes, MongoDB is great for structured data (also for semi-structured data). Some pros and cons to consider (with the caveat that I'm painting with a broad brush, and there are exceptions to every rule):

MongoDB over SQL
- MongoDB has a more flexible model (hierarchical documents versus rows/columns only)
- MongoDB is easier to scale horizontally (automatic sharding & built-in async replication, etc.)
- MongoDB schema migrations tend to require less downtime than SQL migrations
- MongoDB really shines when you have a single application using MongoDB as a persistence engine since you can model your schema after the queries you need
- In many cases, MongoDB requires fewer random disk seeks than SQL due to its document structure

SQL over MongoDB
- SQL typically takes much less space on disk due to its static schema
- SQL databases (particularly normalized databases) offer a great persistence layer for sharing between multiple applications
- It's easier to find people who know SQL than MongoDB
- SQL databases scale better vertically

There are probably a good number of other trade-offs, but those are the ones can think of right now.

Hope that helps!
Kripal Gupta
Greenhorn

Joined: Oct 27, 2010
Posts: 4
Thanks Rick for the reply.
Pradeep bhatt
Ranch Hand

Joined: Feb 27, 2002
Posts: 8919

Is mongo db modern version of IBM's IMS database ? IMS is hierarchical database.

http://en.wikipedia.org/wiki/IBM_Information_Management_System


Groovy
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Where to use MongoDB : is it good for structured data