Dale,
there is really no need for an excusion :) I found your pointer really
informative and what you are saying is always interesting. But yeah, Yanni has
a point here. I was pretty satisified with Omnibase because it is easy to
handle being smalltalk and running in the same image. Supporting
Hi Dale,
thanks for the pointer. I always admired what the GemStone people did and do.
But I'm looking for something more lightweight and more easy to handle approach
this time. Well, from the github page I could not derive what it really does to
be honest.
Hope to see you at ESUG,
Norbert
Sorry to have interrupted ... I just remember that folks have moved from
OmniBase to GemStone in the past for "performance reasons" and understand
that those aren't the only reasons for having an OmniBase replacement ...
Dale
On Mon, Aug 8, 2022 at 10:22 AM Yanni Chiu wrote:
> Dale,
>
> It’s no
Dale,
It’s not about inventing a “database”, it’s a requirement to persist data
beyond image start/stop, along with intangibles like having the full source
code to tune for individual requirements. In my case the top (desired)
requirements are single directory or file per user (scaling), and no
ad
Norbert,
Before you go off and invent a data base, you might take a look at GemStone
and RemoteServiceReplication[1] ...
Dale
[1] https://github.com/GemTalk/RemoteServiceReplication
On Mon, Aug 8, 2022 at 6:19 AM Norbert Hartl wrote:
> To all Omnibase and Monibase users.
>
> It turned out that
