Why would people use pure XML databases over plain RDBMs?

Question

How many of you are actually using pure XML databases over RDBMs? The former seem to be gaining momentum, but I don't understand the advantage. Anyone cares to explain?

Answer 1

What do you mean by "pure XML database"? If you mean a text file containing XML, that is not really a database, as it lacks almost all the features of a true database, such as transactions, locking, mult-user access, security etc. etc.

Answer 2

Take a look at this article i guess it might help you.

Answer 3

Conditions that suggest XML isn't a crazy idea

• If your data looks like a collection of documents. For example, novels have structure, e.g. chapters, paragraphs, sentences, words. You might want to access the structure programatically, but it would be hard to make a relational schema that would support that.

• A mind boggling number of fields and tables required, almost all are optional. For example, not all novels have a villain, but a villain attribute or tag would be easy enough to add to an xml document.

• If you have a fairly small amount of data.

• Data is strongly hierarchical. It is easier to query an XML document of a organizational chart than to do the similar query on an employee table with a manager column that links to itself.

Example- DasBlog which uses plain ole xml as the datastore.

Conditions that suggest a relational model is better

• Most of your data fits nicely into tables and columns, fairly small numbers of fields, most fields are required.

• There is a lot of data. The Relational world has been optimizing for performance much longer than the XML database world.

You can have it both ways

• Most modern relational databases support xml as a first class data type.

Answer 4

I fail to see the real benefits of using XML over relational databases without the context.

Relational databases are often clumsy to operate, even though you can easily query about with any requirements from them. If you don't need to do queries on your data then you don't have any real use from RDBMs. How many photos have you seen wrapped into a relational database? Isn't it more convenient to store photos in jpeg or png? In other hand, do you like to store image pixels in XML?

Answer 5

As someone who works on an open source product that heavily uses XML databases, I find XML data sources invaluable as they are representations of the pure data structures used in the program.

XML allows me to model a complex structure in code then serialize it directly to XML to be read in either else where or at a later date, or my specifically in my case export a complex structure in XML then manipulate and query it in memory. There are other options such as ODBMS and ORM which offer many of the same advantages (and then some more), but come with a knowledge or performance overhead.

Answer 6

One advantage that hasn't been mentioned is it's much easier if the data is supposed to be available to the public (via RSS or whatever). If the main use for the data is for some kind of public API, or if it is going to be formatted as XML later anyways, then why not? Say you wanted to store some HTML templates. Wouldn't it be easier to store it as HTML? You'd also save the overhead of an RDBMS and processing the data into XML.

XML is also okay if you do almost all reading and very little writing, although a simpler format such as JSON might be more efficient depending on what you're doing.

In any other case, especially if there is a lot of data manipulation involved, real databases (whether relational, object-oriented, document-oriented, whatever) are going to be much more efficient because they're built for that. XML wasn't meant for 100,000,000 rows of data.

I think the reason some databases use XML is because it's such a widely-used format, especially for things like RSS feeds. Like I said before, if your data needs to be XML in the end, then why not store it as XML and make your life easier?