qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Shaw (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Commented: (QPID-156) Implement persistence to disk for Qpid
Date Tue, 05 Dec 2006 12:55:22 GMT
    [ http://issues.apache.org/jira/browse/QPID-156?page=comments#action_12455616 ] 
Steven Shaw commented on QPID-156:

We could also try ActiveMQ's Kaha store.

Another option is Perst - a low level odbms with store-like interface.


Perst is now developed as a commercial odbms product http://www.mcobject.com/perst/

However the author was kind enought to provide a link to the last release of the code under
a friendly licence:

  http://www.garret.ru/~knizhnik/perst-249.zip   (MIT licence)

At some point it had favorable performance compared to BDB:


After reviewing the design documentation though it looks like multithreaded performance could
be an issue:


Another option is the Consus RDBMS from the same author. It includes a low-level store interface
similar to Perst in some ways.

  http://www.garret.ru/~knizhnik/consus.html  (new BSD licence)

> Implement persistence to disk for Qpid
> --------------------------------------
>                 Key: QPID-156
>                 URL: http://issues.apache.org/jira/browse/QPID-156
>             Project: Qpid
>          Issue Type: New Feature
>          Components: Java Broker
>    Affects Versions: M1, M2
>            Reporter: Marnie McCormack
>            Priority: Minor
> Currently, we only provide an implementation of persistence in-memory using Qpid code.
For persistence to disk we use the Berkeley DB. Would be better to offer an alternative imeplmentation
which allows the use of Apache licensed code for persistence to disk.
> Previously been discussion on dev list regarding best solution for this, including appropriate
API - using O/R mappers, JDBC, in-line SQL etc etc. 
> More implementation details to be added by assignee please prior to progressing this

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message