2) Member usese MySQL atm - it should be straightforward to port to other databases. I'm looking at SQLite for the desktop version for simplicity, and maybe transitioning to a Graph
Go with SQLite, it's awesome. Unless you heavily rely on query optimizer/planner magic then there's nothing faster for local storage. I'm using SQLite for all the various things the
That really depends on workload and SQL features you use. For web software which is accessed by many users at the same time I'd probably stay with MySQL. I think SQLite still has
client app needs to store, but network data are basically 4 tables (and 2 of them being kind-of indices), so I went ahead and again wrote custom fast storage with very little