Hi Butch, i'm using GT.M as a dabase backend for a object oriented datastore with Java. (GTM4J) The programming model is very simliar to db4o. It allows you to store your Java objects without configuration files or annotations. >From my experience with GT.M, i can say that this db is rock-solid, very fast >and scales very well. To give some figures on my development PC (Acer Aspire M7720 Intel Core i7 2.67 GHz): One of the samples i've developed was to load OpenStreetMap data. Thereby the object model stores the data in a unnormalized way. I reach in this configuration up to 8000 objects stored per second. Each object represents a OpenStreetMap 'NODE' which contains Lat,Lon,Tile and a list of Tags. Tags vary in length and contain key/value pairs (created, streetnames, types, etc.)
For me, GT.M seems to be a very interesting database backend wich allows for extreme flexible DB architectures (Key/Value, hirarchical, Relational. -- Lothar -- This message posted from opensolaris.org
