I agree with Ramon and Janko.

My stop condition to start using Magma was that.......the image ever
worked fine to me!

I admit I'm not managing TBs (nor GBs) of data in my current
production systems but, as Ramon comment on his blog, the image works
ok to a wide majority of projects (at least in my own experience
developing systems to small and medium companies).

Ever I found (with few lines of code) the way of ensure integrity,
backups, changes, etc.

Just my 0,02.

Cheers.
gsa.


2008/1/15, Blake <blake at kingdomrpg.com>:
> On Tue, 15 Jan 2008 01:57:45 -0800, Janko Mivšek <janko.mivsek at eranova.si>
> wrote:
>
> > In the case you didn' yet read Ramon Leon post on his blog:
> > http://onsmalltalk.com/programming/smalltalk/simple-image-based-persistence-in-squeak/
> >
> >  From the post:
> > . . .No object relational mapping layer (not even Rails and
> > ActiveRecord) can match the simplicity, performance, and speed of
> > development one can get just using plain old objects that are kept in
> > memory all the time"
> >
> > Image as a database is my way of running my web apps for four years
> > already, and I make my living of them, so I can just agree and confirm
> > Ramon here!
>
> How do you handle reporting in that situation? Particularly reporting
> using 3rd party tools?
>
>         ===Blake===
>
>