>From the very beginning, the idea of a pluggable data store has been part
of the architecture. We've done it once -- originally we were using "gdbm"
but because that was so unstable we switched to Berkeley DB.
dothebart would undoubtedly want to use ArangoDB.
I'm ok with it as long as it does NOT destabilize the code base. We've been
on Berkeley DB for a long time now, so the code is probably a bit ossified,
and we'll need to do some work to get back that loose coupling we need. Yes,
everyone loves to hate Oracle, but the Berkeley DB code is ABSOLUTELY ROCK
SOLID and we don't want to gain a reputation for unstable performance -- that
honor belongs to Exchange alone. :)
But yes you are correct: I want to get *everything* into the database. No
flat files anywhere. This includes things like the netconfigs and bio and
userpics etc etc etc. This will make the XML export
format a lot easier to work with too, because it will *include* all of those
pieces without having to rsync them over from system to system. A single
dump file really will cover the whole Citadel installation.
Since the pluggable DB would be something configured at compile time --
switching
databases on an existing installation would be a matter of exporting to XML,
recompiling Citadel Server with a new database back end, and loading the dump
file.
