On Tue, Nov 29, 2011 at 10:49 AM, Jason Kölker <jkoel...@rackspace.com> wrote: > On Tue, 2011-11-29 at 16:20 +0100, Soren Hansen wrote: >> >> It seems I've talked myself into preferring option e). It's too much >> work to do on my own, though, and it's going to be disruptive, so we >> need to do it real soon. I think it'll be worth it, though. > > I agree. This will also make it easier to swap out the storage with > other Non-SQLAlchemy datastores *cough* ElasticSearch *cough*.
There's a very good reason this hasn't happened so far: handling highly relational datasets with a non-relational data store is a bad idea. In fact, I seem to remember that is exactly how Nova's data store started out life (*cough* Redis *cough*) -jay _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
