Alternatives to MySQL [closed]

Answer 1

If you want something really scalable, I wouldn't opt for a flat or XML file. As your data grows, it could kill your performance.

If you will have a lot of data at some stage, I would still opt for a database - I would take a look at something like SQLIte with a very simple schema to suit your needs.

Answer 2

If your writing a java program that wants an imbedded database look at hsqldb since it is written in java and works much better then sqlite if being called from java programs.

Answer 3

If you are writing Java, then there are Java database implementations (Jared mentions hsqldb, there are others) that you can directly include.

SQLite is fine for static inclusion, however you can also include MySQL within your application if you're using a compatible language such as C.

I think you would appreciate having SQL available as well. XML files just don't cut it any longer, maybe a couple of years ago when writing PDA software, but even the iPhone and Android includes SQLite now.

Answer 4

if you want a 'persistent cache', and already use memcached, check memcachedb. it's a persistent hashtable using the memcached protocol, no need for a new client (but a new daemon)

Answer 5

For Key=Value pairs, you can use INI file format with simple load and save procedures to load it and save it to in-memory hash table.

That can later scale up to anythig, just by changing load and save procedures to work with db.