Data ex-multiplication - Jeux multiplication en ligne
You need software that manages data. Large amounts of data. Or data with complex, unusual structure. Or data in unusual hard and software environments. You need to evaluate unusual queries on your data. You have unusual performance requirements. Maybe all of the above.
We can help you.
data ex multiplication is a team of experts in analysis, design, implementation, deployment, jeux pour apprendre les tables de multiplication and evolution of database management systems. Our main objective is to make our native XML Repository Natix the favorite XML database management system for all XML applications.
- Table de 1
- Table de 2
- Table de 3
- Table de 4
- Table de 5
- Table de 6
- Table de 7
- Table de 8
- Table de 9
- Table de 10
- Table de 11
- Table de 12
- Table de 13
- Table de 14
- Table de 15
Browse this web site to find out more about us. Or just drop an email and challenge us with your problems.
data ex multiplication GmbH was established in August 2000 as a spin-off of the University of Mannheim's database research group. We are currently based in Heidelberg.
The founders are
- Our chief architect, Dr Guido Moerkotte, who is Professor of Computer Science at the University of Mannheim and has a long record of high-quality publications in database research.
- The current general manager, Carl-Christian Kanne, who has over a decade of experience in commercial software development.
- Dr Till Westmann, who, in his PhD thesis on efficient database runtime systems, developed a lot of the technology that is used inside our XML repository Natix.
The Natix XML Repository History
Several years ago, when XML first came around, as database researchers we did our job: Thinking about how to support a data model such as the one used by XML with a database management system (DBMS). We quickly found out that none of the existing DBMS could adequatly be customized to support XML, despite all claims of their vendors.
The XML repository wish list
A DBMS worthy of the term XML "database management system" would need to support compact storage of structure and content of XML documents, index structures for content and structure retrieval, validation, recovery, isolation of multiple users that work on the same document(s), query evaluation, a rich set of application programming interfaces (APIs) for languages like C++, Java, and support for legacy applications. The system would need to scale in many dimensions, like number of documents, size of documents, query throughput. The system would have to be modular, so you don't have to pay performance penalties for features you doesn't use. It would have to be easy to install and maintain. It would have to run on all the typical server platforms. Needless to say, it would have to be faster than the mixture of tools with which those functionality currently was approximated.
XML is not just any database application
We found out that some of the above can be achieved by some of the traditional DBMS, but only at cost in performance and convenience, because XML support, and thus optimization for XML, would be limited to one part of the DBMS, the "XML module". To achieve all the requirements above with best possible performance, the system would, in all its components, really have to understand XML. It would have to be what we call native.
Natix was born
So, we started to develop our own native prototype XML database management system, called Natix.
After forming a company, during our work in data management consulting we learned that the expectations put in XML are rapidly coming to life. Many organizations are developing applications that need to manage large amounts of XML data, and require data management software with the functionality of a true database management system (DBMS), but the developers still do not find appropriate database software for XML. On the other hand, Natix seemed an ideal foundation for the job, because it already contained designs to address all requirements listed above.
data ex multiplication is now polishing Natix to provide full DBMS services to XML developers. Even if you think you do not need it today, you will hear about it. Soon.
Current State of Natix
The current Natix kernel has still a lot of functionality missing from the list of things we expect an XML database to do. Most notably, the transaction support is not finished, and the external API is being cleaned up.
There is a demonstration version available that allows you to experience Natix' technology.
Although you cannot buy it shrink-wrapped, it is possible to license the Natix kernel in its current state. We are interested in making your application a Natix-based solution, learning more about your requirements, and to tailor Natix to your needs, just contact us.
Custom Natix Solutions
Natix is not a finished off-the-shelf product yet, but it can be licensed and is in commercial use as powerful library for storage and processing of XML. Maybe your applications can already benefit from using the current Natix kernel.
We are very interested in learning your requirements for XML repositories. Maybe, after inspecting the demonstration version, you have ideas about features that would make Natix more suited to your purposes.
Maybe you have an unusual environment in which you need an XML repository (mobile phones, PDA, television, embedded systems, ...) and you would like to know if Natix can be customized to do the job.
In all of the above cases, we would be very happy if we can help you to develop a Natix application.
Download Technology Demonstration
We are still working to polish Natix for you. To allow you to get a first glimpse at Natix, we invite you to download a technology demonstration.
If you register in the form below, you will get to download the NatixFS file system interface. It is a sample application of the Natix kernel, which presents a file-system view of an XML document collection and allows you to import and export documents to and from Natix from any program that can create or read textual XML files (e.g. editors, office software, web servers, but also plain Unix commands like cp, mv and cat)! You can also evaluate XPath queries on your data from those programs. Just give it a try.
REQUIREMENTS:To install the demo, you need a Linux system with kernel version 2.2.16 or later (2.4.x is fine) with CODA support enabled in the kernel. Most current distributions already have CODA support enabled, so you can immediately try NatixFS (you can call "/sbin/modprobe coda" to verify).
Management of Persistent Data
During initial application development, managing persistent data is frequently viewed as a minor aspect of the software. Later in the development cycle, it becomes clear that data management is a discipline to itself that often influences the complete application architecture.
The data ex multiplication team can help you to understand, and meet, the needs of your software that originate from persistent data management. We can contribute to any of your development activities (We call them activities, and not "phases of development", because every software developer knows that the development process cannot be strictly separated into phases which follow each other in a strict sequence or circle).
Don't hesitate to contact us if, after looking at the situations below, you suspect that we should work together.
|Essential for every successful application is a suitable model of the application domain. We have built models for a great variety of complex domains, including biochemistry, mechanical engineering, mail distribution and others. Such models (often expressed in a modeling language like UML) can also provide a base vocabulary when talking to your users.|
|Use cases are stories that describe interactions of users with your software systems. They are a very powerful means of communicaton between potential users and the software developers. As a side product of our domain modeling work, we are experienced in dealing with use cases, can help you to write better use cases and make sure they contan the information the developers and customers find helpful.|
|Having those prerequisites, we can analyze with you what your application requires with respect to persistent data management. Usually, not all of the data needs to be persistent, and not all persistent data is used in the same way. It is very important to classify your data and to determine in which way it is going to be accessed, if you want to evaluate queries, how much data of each kind the application will have to deal with etc.|
|Based on the requirements of your application, you have to design an architecture. Which data model and which database management system (DBMS) to choose and how to integrate them into your application are decisions that can make a tremendous difference in effort and cost when you start implementation.|
|Very often, application programmers then just fire away and create the data structures (tables, class definitions, DTDs,...) inside the database system without much thinking, because they "already know what the data looks like". But usually, there are several alternative ways of designing the database schema, and if you do not compare at least some of them, you will very likely end up with a schema that makes implementation, maintenance, and evolution ineffective and costly. We are experienced schema designers for any data model, and can produce clean and effective schemas for your application.|
|To get the most performance out of your data management architecture, careful physical database design is necessary. Our assistance in selecting index structures and partitioning schemes of your data, or maybe even creating special indexes four your data access profile, can be a crucial factor in speeding up your application.|
|While most of our implementation resources are bound by Natix development, we always try to find room in our schedule for particularly challenging contract work, e.g. implementation of novel index structures and specialized storage formats.|
|But maybe you should contact us anyway, because some of your specialized needs can be satisfied by Natix, which contains configurable, optimized modules for a variety of data management tasks.|
|Deployment||After software construction, sometimes the performance of the system does not meet your expectations. This may result from changed requirements, or unusual customer environments, or maybe you don't know at all why things don't work out as planned. By careful interpretation of the system's runtime behaviour and fine tuning the DBMS, we can maybe fix the problem without large changes and development work.|
|After the users understand your software and feel comfortable using it, there soon will be new, and changed requirements, or even completely new ways of using the application.|
|You certainly don't want to redesign everything from scratch, but just welding on extensions without thorough planning is leading to complicated, difficult to maintain systems, and before long you will have to redesign everything.|
|Working with us can show you the appropriate points to evolve your software are. Maybe the model is more flexible than you thought, or there are lesser known features of the DBMS, and you don't have to change that much after all!|
Data ex multiplication GmbH