Is dead….

I got rid of it over the summer. Raydo started out doing it’s own messaging/server/client thing. That was fine, it needed its own backing store then.

Now since we are using a message store, the message store can take care of persistence now.

The most interesting store is the BDBMessageStore on Qpid. The BDBMessageStore module utilises the BerkelyDB to provide persistence. Cool.

Anyway, the backing store code has been ripped out, thank you very much.

     I cleaned up the C++ interfaces a little bit. This image below is only for the C++ interfaces.

    I am concentrating on Postgres, sqlite, Oracle and MySQL. Postgres and SQlite have the most project friendly licenses, and MySQL / Oracle have the least friendly licenses.

    However, the cluster aspects of MySQL and Oracle are awesome. Something the other two do not have.

( I know Postgres has clustering, but it is not the same )

I have been doing a lot of work with Java. A lot of it in getting the     C++ and Java interfaces to align. So when I went looking for a database engine, I settled on H2 for the Java engine.

    Since you can run Raydo in an application, H2 can be run in an embedded mode, as well as HSQLDB and Derby. It can also be run as a client / server and a cluster.

The ‘plugin’ was added to the Java tree.
    So looking at the benchmarks, it seems that H2 is faster than HSQLDB & Derby in the embedded space, and comparable with Postgres and MySQL in the client/server space.

    When I started Raydo, I wanted a very easy to use framework. Something that would not take too much time for others to use/develop, etc. So I went with a C++ framework for speed.

    All is good, except there is a lot of java code in this space, even if it is slower than compiled C++. Yes, I know about gjc.

    I would like to implement a native java driver into the source code for sqlite. That will give us a mixed mode environment in the future. Raydo ‘lives’ on the underlying database, so if I was to include java, the database would have to be accessible. And when I mean accessible, I mean easily accessible. Not requiring users to jump through a billion hoops.

    So when I can add sqlite support to Raydo, I will start rolling in the Java code I have.

    I have implemented sqlite as the first database plugin. It is not really a ‘plugin’ in the sense that you have to compile it in, but in the sense that it is a pluggable architecture. I am using a factory pattern as such., however I think that most users are going to pick a database and stick to it.