Am 17.12.2012 um 19:08 schrieb Torsten Bergmann <astares@gmx.de>:
Persisting data is crucial for any application and there are many ways to do it. Be it RDBMS, NoSQL stuff or in-image persistency. There are many pre-built solutions: Gemstone, OpenDBX, SandstoneDB, Mongo, ...
From time to time I ask the question here on the list to see how it evolves and what people actually use in their Pharo applications:
1. What persistence option do we currently have
I like to add plain fuel. I store e.g. configurations with it as these change rarely. For reliability I applied a sequence file to it. Meaning I write files with .fl.1, .fl.2, etc. and a file seq containing the last written number extension. The mechanic is to first write the fuel file and then overwrite the seq file with the actual sequence number (if a write fails the seq file isn't changed). Reads are reading first the seq file and then the fuel file.
2. What persistence is used in your Pharo application today
GemStone, MongoTalk (maybe soon it will be voyage, too), Fuel, Sixx. And in testing phase riak (no phriak, yet).
3. Which persistence solution you want to use/would you like to see in Pharo's future
A decent implementation of LOOM. I think as long as there are different types of memory (main memory, disc storage,..) this is something nice to have.
4. What would you recommend.
Reify object references :) Norbert