Lists Home |
Date Index |
- From: Kay Michael <Michael.Kay@icl.com>
- To: "'ROB.S.HINES@nttc-pen.navy.mil'" <ROB.S.HINES@nttc-pen.navy.mil>, email@example.com
- Date: Wed, 25 Aug 1999 12:32:17 +0100
> Being a newbie to the group I have what I consider a
> burning question, but has probably already been hashed out. If someone
> point me in the right direction I would be quite appreciative. Basically I
> make some decisions regarding my position on Repositories for XML data,
> specifically Computer Based Training developed in XML. There will be
thousands of courses
> residing in the repository, served up world wide.
> My initial position was to go with an Object Database, in
> something built around a solution like POETS Content Management System.
> there have been many individuals that dislike this idea, and balk at the
> leaving the safety of the well know RDBMS community.
We've made this journey and learnt quite a few lessons from it.
We were using an object database (an early version of Jasmine), but after a
couple of years we reverted to relational databases. The reasons:
- people were storing data in very fine-grained form and it took ages to
reassemble for display. It's better to store the data relatively
coarse-grained and split it up (by parsing) when you need to.
- we hit a skills bottleneck, there were only a few gurus who understood the
- the class library was getting ridiculously complex, we weren't achieving
enough re-use across different projects to justify the generality of the
- we hit immaturity problems with the technology (e.g. lack of low-level
performance monitoring and tuning tools) - the kind of boring things where
20-year-old products like ORACLE really score.
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)