Your documents are likely to have a less regular structure and things such as entity usage are probably important to you because they are a fundamental part of how your documents are structured.
In this case, you might want a product like a native XML database or a content management system.
It is much easier to invent a small XML language and write a SAX application for interpreting that language than it is to write a parser for comma-delimited files.
In addition, XML allows you to have nested entries, something that is harder to do in comma-delimited files.
Thus, while it may be possible to use an XML document or documents as a database in environments with small amounts of data, few users, and modest performance requirements, this will fail in most production environments, which have many users, strict data integrity requirements, and the need for good performance.
A good example of the type of "database" for which an XML document is suitable is an file -- that is, a file that contains application configuration information.
NOTE: Although the information discussed in this paper is (mostly) up-to-date, the idea that the world of XML and databases can be seen through the data-centric/document-centric divide is somewhat dated.
Not only do you want to manage the site, you would like to provide a way for users to search its contents.It is a good bet that your data has a highly regular structure and is used by non-XML applications.Furthermore, things like entities and the encodings used by XML documents probably aren't important to you -- after all, you are interested in the data, not how it is stored in an XML document." An XML document is a database only in the strictest sense of the term. In many ways, this makes it no different from any other file -- after all, all files contain data of some sort. For example, it is self-describing (the markup describes the structure and type names of the data, although not the semantics), it is portable (Unicode), and it can describe data in tree or graph structures. For example, it is verbose and access to the data is slow due to parsing and text conversion.A more useful question to ask is whether XML and its surrounding technologies constitute a "database" in the looser sense of the term -- that is, a database management system (DBMS).However, this is hardly a database, since it is read and written linearly, and then only when the application is started and ended.