Slashdot Mirror

← Back to Stories (view on slashdot.org)

Daffodil DB / One$DB - How Do They Compare?

Posted by Cliff on from the collective-experiences dept.

capt.mellow asks: "It's been mentioned that Daffodil Software has just released php extensions for their java-based commercial and open-source databases, Daffodil DB and One$DB respectively, enabling these databases as options for running web applications. Personally, I have never heard of these databases before. How do they compare to the likes of Oracle, SQL Server, MySQL, PostgreSQL, Firebird, SQLite, et. al.? Has anyone used them in web applications, and would they care to relate their experiences?"

3 of 36 comments (clear)

  1. Sounds like good products by FullMetalAlchemist · · Score: 3, Interesting

    Sounds like good products.

    However, there already is SQLite and PostgreSQL that covers the entire spectrum; up untill Oracle is needed.
    As I unfortanly doubt that these databases compare to Oracle, so they are in essence racing with a dead horse; it really might be a beautiful dead horse, but it's still dead.

    I really like new things, but they are pushing their luck when introducing a database into an already overcrowded market.

  2. No by Pan+T.+Hose · · Score: 2, Interesting

    In this light; is SQLLite really any faster than either MySQL or PostgreSQL in real-life, production situations?

    The short answer is: no. The long answer is: it depends on what you mean by real-life, production situations. The real question is: should you worry about it before it starts to be a problem? Or a better question: what do you have to do when it starts to be a problem? And if your applications are designed correctly, the answer is:

    shell$ sqlite old-db .dump | psql new-db

    and update data sources in your applications. You only have to use abstraction layers in your programs, like DBI in Perl, and all you will have to change is one argument to DBI->connect() and the rest will just work, because PostgreSQL supports a superset of SQLite features. I'm not sure with MySQL, so you'd have to do some research. But the point is that the most important things one should consider while choosing a RDBMS (other than ACID) is the question how easy is it to get your data out of the database and insert it somewhere else, because then the question which database is better in the long run is not so important, for you can always change it later if you want. The keyword is: abstraction layers.
    --
    Sincerely,
    Pan Tarhei Hosé, PhD.
    "Homo sum et cogito ergo odi profanum vulgus et libido."
  3. Re:SQLite by jbolden · · Score: 2, Interesting

    In this light; is SQLLite really any faster than either MySQL or PostgreSQL in real-life, production situations?

    SQLLite can be as fast as pure data caching to disk for inserts. When you have data coming into the system so fast that a real RDBMS couldn't handle it (on the same hardware) and are willing to have very slow queries until the data is moved over SQLLite rocks. That's a pretty specialized production situation but I had to implement.