[quote=“Ragosch,post:40,topic:27474”]
Very expensive hashtable with transactional behaviour. ‘transactional’ is quite a major point I suppose.
Correct, I forgot to mention that. But it is still like using a Mac truck for the transport of a six-pack.
Ragosch
To be complete: a highly scabalbe, transactional, fault tolerant and snapshottable hashtable 8)
.Id say we are uign about 50% of its capabilities.
what do you mean by snapshotable?
Being able to pull a referntially integrous external backup without bringing the system down.
Hm, yes, it is true, that is a nice feature too. But I would not say that those missing relational database features, query and manipulation abilities would just count as 50% of the database features. If you are used to express and query your data in relational tables you will heavily miss those if they are no longer there.
Ofcourse some of those features could be intergrated using an external database from inside the SGS via the SimTask.openSocket(…) method and the associated callbacks via a GLO, but it would call this GLO 3 times for a single query, while an implementation via a new SimTask.startSQLQuery(…) method could do this by just invoking the callback GLO once (maybe with an automatic deletion of this GLO when this callback task ends). Wouldnt that be a much more efficient way to use relational database features from inside the SGS?
Ragosch
jeff, i would like to know more about the backend objetc store(HADB). wonder if http://www3.java.no/JavaZone/2005/presentasjoner/ManyiLu/ManyiLu-JavaZone.pdf has some similarities to the ObjectStore at SGS backend?
That link is also that info I read about the HADB technology - it is a highly accessible database capable to repair itself when an error occurs. Jeff said, HADB is planned as backend storage in the “big” version of a SGS installation, afaik.
Ragosch
HADB is indeed a technolgoy we are looking at striongly for objectstore implmementation.
We have some large scale scalign concerns that may result in our adding to the HADB model to support. This is all in heavy research right now.
How about a criteria query type interface that hangs off SimTask with the results redirected to either a callback or a channel?
Sorry for the thread necromancy 