Why an embeddable database engine

In contrast with most native XML databases, Qizx/db is not (yet) proposed as a classical server with remote client connections, but as a bare embeddable multi-threaded engine.

What does it mean in practice ?

1. Qizx/db can be used in a Web Application: a typical use, where Servlets or Web Services offer a business-specific access to an XML database.

   In such a case, Qizx/db is used directly by the Servlet container, which provides the best throughput.

2. Qizx/db can be used as a component of a standalone application: for example to implement a sophisticated diagnostic and maintenance tool exploiting a database stored on a DVD.

   Or it could also simply be used for its capacity to handle very large amounts of XML data efficiently.

3. The bare Qizx/db engine can also of course be used to implement a classical database server. This will be part of a coming release: see roadmap.

In terms of API, Qizx/db has been designed with a concern for:

• Simplicity.
• Generality.
• Extensibility and openness: many features of the engine can be redefined or extended. For example there is an generic access control mechanism for controlling which parts of a database a user connection can access. An application-specific implementation of this access control can be plugged. Similarly it is possible to add observers, data converters, to customize indexing.