Le 09/06/2015 14:48, Mariano Martinez Peck a écrit :
For Quuve app, when it runs on Pharo (for development and testing), we have a fuel backend and we do 2) and 3) of above. Quuve itself is split in different/isolated conceptual databases: clients, advisory, securities, system, application, etc. So each of them is a database. And yes, we have a fuel file per database and for each save we serialize the whole graph. You need to be careful about cross-references between databases.... Anyway, it works good enough for our scenario. Our database are around 5MB and the serialization is immediate.
The perspective looks great. I don't need concurrent write access, and I am anticipating the graph remains far bellow 5MB, likely bellow 100 KB. I am just testing it and one fuel file per graph looks great, and it is so comfortable! Thanks Hilaire -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu