Hello,

I am looking for the alternatives to the MSE format for model persistency. The current problems I see with MSE:

- It is all or nothing approach (hence loading takes time)
- need to add entities to model to be able to store them on the disk and this approach does not work well when you want to persist duplication information, caches and annotations.

There was a Fuel-based solution and I am wondering if it can be helpful.

While looking for persistency solutions for Pharo, I came across several solutions like Voyage/Mongo, GLORP, StandStoneBD, and Magma.

http://www.seaside.st/documentation/persistence

Did anyone try any of these tools in the context Moose? I would do a pilot (saving n retrieving a test model, playing with caches and properties) with Voyage/Mongo to understand the impact of their usage.

Usman