Laurent, I realize you are asking this on the Pharo list, looking for a Pharo-specific answer. You should also post your requirements on the GLASS list (http://forum.world.st/GLASS-f1460844.html). A number of people/businesses there use a /develop on Pharo, deploy on GemStone approach/. They will be able to give you some good advice on using GemStone/S for your database.
We need a web stack and we put Pharo & co in the comparative process. My team have strong experience in load-balanced php / mysql deployment that handles millions of records but we are ready to build on something else though MySQL is still a requirement. Thanks for Garage + Glorp, I can prototype things. I wonder how to handle database schema migrations. With our PHP projects we have versionned PHP scripts that are automatically run given a database revision number ( see http://git.afi-sa.fr/afi/opacce/tree/master/cosmogramme/sql/patch ). What are the practices with Glorp ? We try QCMagritte and we enjoy what we see so far. What are the best practices to glue Magritte and Glorp together ? Especially when you load-balance requests on several images. Some examples ? ( FYI, I cannot load QCMagritte in a fresh Pharo 6 image ( for #stable version, MADescriptionBuilder missing. For #development versions of Magritte and QCMagritte, QCConfiguration missing ). So actually I use the one built on CI. ) May be you have some other suggestions on a framework you love ? Best regards, Laurent Laffont-- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html