Performance of XML Servers


Performance and scalability: Performance of XML Servers

  1. Performance of XML Servers (1 messages)


    Recently, there exist many XML servers on the market (eg Tamino) that allows you to store XML documents natively in its XML-native store without conversion to/from a relational model. Is it just a gloried OO database or is it really the holy grail for XML data storage?

    Has anyone tried this?

    According to Tamino's website:

    "Relational database management systems (RDBMS) may appear to be a possible choice to facilitate the exchange of XML objects. Unfortunately, the table-based data model of the RDBMS does not suit the hierarchical and interconnected nature of XML objects. An RDBMS would need to break an XML document down into a multitude of interrelated tables. A query against this database would result in many relational retrieval and join operations, requiring high processing power to overcome a considerable degradation of performance.

    In addition, RDBMSs and more advanced DBMSs, such as multi-dimensional relational databases or object-oriented databases, cannot handle data with dynamic structure, which is the key to XML's extensibility. An XML database must be able to store and retrieve any well-formed XML document, even if the DTD of the document is not available.

    An RDBMS, however, needs schema definitions for each table, so a document with an unknown tag would require a change request for a new schema definition, to be built and approved before it can be put into production.

    Likewise, in an object-oriented database a new class definition would be necessary, which is too time-consuming for Internet applications. Native XML storage is the essential method to avoid these performance limitations that are a crucial factor in the evolving high-speed world of e-business."
  2. Performance of XML Servers[ Go to top ]

    hello Benedict!

    What do you mean by native xml store or natively storing an
    xml documents

    Madhu Tera