Posted by Esteban A. Maringolo on Oct 06, 2020; 6:22pm
URL: https://forum.world.st/Easiest-light-weight-cloud-web-persistence-for-Pharo-tp5123027p5123073.html

Hi Tim,

I think that the persistence you choose will depend heavily on a few things:
- The complexity of the objects graphs in your domain models
- This architecture of your system
- How these objects/data is acceded (Atomically/In clusters)

In any case, for a lightweight solution you go the Fuel path, or something
using SQLite.

I have a GLORP based application (small, ~40 persisted classes), SQLite is
so lightweight that I run my SUnit tests creating the whole database _on
disk_ from scratch on setUp and destroying it on tearDown), and only run it
against the production backend (PostgreSQL) before deploying, but even this
is happening less frequently since I'm confident that things will work the
same on both.

OTOH I'm finding that ORMs are burden, and unless you need to work with an
existing schema or you really want to use an RDBMS, you might be better off
avoiding them. I've been using ORMs for almost two decades, so that's still
my default choice, but I feel winds of change here :-)

Regards!




--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html