XML flat file vs. relational database backend

Question

Most projects now need some form of a database. When someone says database, I usually think relational databases, but I still hear about flat file XML databases.

What parameters do you take into consideration when deciding between a "real" database and a flat-file XML database. When should one be used over the other, and under what circumstances should I never consider using a flat file (or vice versa a relational) database?

Answer 1

There is no such thing as a xml flat file database. Flat xml files are non-databases in that they have no higher functions like indices - have fun with larger datasets and searches or analytical queries without any index.

XML databases are another topic and may have their needs (content management, document storage in general - complicated schemata you dont care too much from the database point of view).

Flat files are fine for things like settings 8smaller files), but a real database is a real database. ACID conditions are hard to guarantee for flat files.

Answer 2

To add to Rachel's answer.

• concurrency
• read vs. write

If you have something simple that's going to be read often and is not going to change much it might be more optimal to use a flat file and save the overhead.

On the other hand, if you have to support multiple connections that are going to be adding and updating the data you'll want to use a database.