Web stack practices (Glorp / QCMagritte)

Laurent, I don't have answers to all your questions, but we use Glorp & Seaside (no Magritte) on VA Smalltalk for our cloud service (http://kontolino.de). Am 18.09.17 um 12:22 schrieb laurent:

Hi all, it's been a long time :) At work we are currently comparing several technologies to start a business project that will hopefully be used by thousands of people for several years ;) 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.

Sounds interesting.

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 use a similar approach: our Descriptor class has a method called schemaVersion, which just returns the current version number. We also have a "magic" table for settings in our DB, just holding a "name" and a "value" column, both being Varchars. One of the rows has a name of "SchemaVersion" and the value is (you guessed it) the printString of the version number. Our images accept a few command line paramters, one of them being --upgradeSchema. It compoares the number in the DB with the one provided by the descriptor. If they match, the image quits. If not, it calls all methods named #upgradeSchemaToVersionXXX until it reaches the number in the Descriptor. Thus we can do both SQL based migrations, like DDL stuff, as well as Smalltalk object based migrations (which can be sooo much faster to implement for complex cases). And we have all versioned and maintained in our beloved Envy repository ;-) . The rest is just bash script magic (like only starting one image with the --upgradeSchema parameter and only start the real web workers once that one has ended succesfully). About load balancing: You need Sticky sessions, so no failover between images. If one image crashes, the user must re-logon on a new image. Works nicely with Apache, I guess nginx works as least as well. For Apache, look for mod_prox_balancer to learn more. Hope I could give you a few starting points for your research. And I also hope you'll find Pharo+Garage+Glorp+QCMagritte a good fit for your project. We all want success stories ;-) Joachim

--

----------------------------------------------------------------------- Objektfabrik Joachim Tuchel [hidden email] Fliederweg 1                         http://www.objektfabrik.de D-71640 Ludwigsburg http://joachimtuchel.wordpress.com Telefon: +49 7141 56 10 86 0         Fax: +49 7141 56 10 86 1

On 22 Sep 2017, at 10:28, laurent <[hidden email]> wrote:

Hi Stephan,

actually the difficult part is how to manage correctly Glorp sessions/connections and update of objects in database. My team is quite sad because QCMagritte and Glorp looks nice but we lack experience glueing both together and could not find any documentation on the subject.

Laurent

Le mer. 20 sept. 2017 à 11:53, stephan <[hidden email]> a écrit :

On 18-09-17 12:22, laurent wrote:

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. )

I really like describing domain objects with Magritte and using chains of visitors to add cross-cutting concerns like translations, styling and access control. The resulting domain code is very clean and DRY. To map to database/Glorp I would just add properties to the description wherever needed, and add a visitor creating the mappings. We didn't need that as we developed in Pharo and deployed on Gemstone. At the moment QC generates applications using jQuery, and the live updating needs a round-trip to the server. You might want to substitute that with something that does more client side. I haven't looked in detail at what Johan Brichau is doing. An open issue is live updates that update each other. That needs automatically calculating dependencies and update order. I've copied the latest configuration and added #'pharo6.x' but that is not enough. Stephan

On 22 Sep 2017, at 13:35, H. Hirzel <[hidden email]> wrote:

On 9/22/17, Diego Lont <[hidden email]> wrote:

There is actually a tutorial included in the framework itself.

Great!

One you have
it loaded, you can start the webpage to localhost:8080 and there you have
your tutorial. But this tutorial should be on a external webpage … one of
the things on my todo list.

No problem if the tutorial is included in the framework. I just need to know.

Where is the repository of QCMagritte?

On 22 Sep 2017, at 12:55, H. Hirzel <[hidden email]> wrote:

On 9/18/17, laurent <[hidden email]
<[hidden email]>> wrote:

Hi all,

it's been a long time :) At work we are currently comparing several
technologies to start a business project that will hopefully be used by
thousands of people for several years ;)

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 ?

Maybe you have a look as well at
https://railsexpress.quora.com/Pharo-Seaside-Express
<https://railsexpress.quora.com/Pharo-Seaside-Express>
(referenced in another thread).

Use Smalltalk as modeling  / design tool and generator. Then the run
time is done with another technology.

Best regards,

Laurent Laffont