While much has been written about XML data storage, none of the research to date has focused on the key questions:
In attempting to understand the answers to the above questions, ZapThink realized that there was no single answer for any of these key questions. In fact, it seems that the various requirements for XML data storage pull end-user customers in different directions when they are deciding how to implement XML storage requirements. As such, this study seeks to do what no other study before it has done: show that XML data storage is not a distinct market segment, but instead a functionality requirement for applications that require XML storage in order to achieve their overall system objectives.
Going forward, expect such native XML databases to become more common as the use of XML to represent all kinds of data spreads, says Ron Schmelzer, an analyst at Zapthink LLC, an XML consultancy in Waltham, Mass. XML databases are better than traditional ones at preserving XML hierarchies, says Schmelzer.
For example, a document can be stored as a document instead of being shoehorned into rows and columns, Schmelzer says.
Tamino was the first to market and remains on top. But a number of other vendors, including IxiaSoft Inc. and Neocore Inc., offer similar products.
In the future, expect to see vendors of traditional relational database management products, such as Oracle Corp., ship native XML databases as well, he says.
Read more at: Computer WorldIpedo has developed a proprietary, hierarchical, in-memory database engine aimed at storing XML documents "natively". The Ipedo XML Database uses memory techniques to get substantial performance gains versus some other NXD approaches. Built as an all-Java server, the Ipedo system is meant to be easily integrated with typical application server environments. Ipedo has extended XPath for search across multiple XML documents and has also included XSLT transformations within the data store itself.
The most valuable attribute of Native XML Data Stores (NXDs) is their ability to store arbitrary and highly variant XML documents. XML-enabled RDBMS systems require explicit mappings to XML documents, and by their very nature are unable to deal with XML documents that have a highly variable structure and take advantage of XML’s extensibility capabilities. X-Hive provides a solution to this problem by presenting a highly scalable NXD system that is capable of supporting a large quantity and volume of XML documents. X-Hive/DB is differentiated itself by its focus on high volume XML data storage requirements, support for advanced XML query and storage specifications, and focused support of its European customer base.
The only true solutions for enterprise-wide XML data storage and retrieval are XML-enabled RDBMS and Native XML Data Store (NXD) approaches. The challenge with XML-enabled RDBMS is that they are not very well suited to highly extensible and flexible documents, while the challenge with NXDs is that they are unproven technologies with very small user bases. However, there is another option that is a sort of "middle ground": the use of an interpretive middle layer over standard RDBMS systems that offers schema-independent, "native" XML data storage. In this vein, B-Bop offers their Xfinity Server as a way of providing the features of Native XML storage while utilizing existing relational storage architectures.
Rather than being forced to map XML documents to an alternate data representation format or insert an entire XML document into a single field as is the case with XML-enabled RDBMS, the Native XML Data Store (NXD) can accept XML documents for storage and retrieval without any modifications, mapping, or transformations. NeoCore provides a patented NXD approach that assigns a unique fingerprint called an "icon" to each XML document and then applies hashing and storage techniques to these iconic representations. This approach allows the user to experience speed and indexing improvements over other methods of XML storage and retrieval and exploits XML structure by self-constructing the data store, reducing development time.
While file systems, relational, and object-oriented database management systems have met our needs in prior years for data storage and retrieval, XML imposes new requirements on how that information needs to be stored so that it can be retrieved in a structured, hierarchical manner. This ZapThink report, “XML Data Storage Technologies and Trends” covers the various commercial options that focus on meeting the requirements for XML storage and retrieval, and identifies benefits, disadvantages, key market drivers, and sizing and growth of the market for these products.
While file systems, relational, and object-oriented database management systems have met our needs in prior years for data storage and retrieval, XML imposes new requirements on how that information needs to be stored so that it can be retrieved in a structured, hierarchical manner. This ZapThink report, “XML Data Storage Technologies and Trends” covers the various commercial options that focus on meeting the requirements for XML storage and retrieval, and identifies benefits, disadvantages, key market drivers, and sizing and growth of the market for these products.
Download File
In financial services, the picture is murkier. Plenty of financial service providers have implemented XML. But too many companies are trying to be the first to gain a competitive advantage with XML-based systems, and then force their own standards on their partners. The result: confusion, acrimony and duplication of effort, says Ron Schmelzer, founder and senior analyst with XML market researcher ZapThink LLC.
Read more at: CIO Insight
SOA Implementation Roadmap