Re: suggested persistence approach for new app

interesting , I have not been on te Pharo discord channel for a bit and
guess I missed discussion about Soil.
Sounds like the Ominbase db that was around for a while.

On Thu, Apr 6, 2023 at 8:47 PM Yanni Chiu <[email protected]> wrote:

> Charles,
>
> You might consider porting Soil database, which is currently being created
> in Pharo. It’s just pure Smalltalk plus file locking OS calls. Of course
> you can’t be risk averse, since there isn’t even a first release yet. The
> payoff would be big, since you get to drop the entire black box of database
> code.
>
> I started with postgres on my stuff, worked on Gemstone code for others,
> went to mongodb for my (yet to be deployed stuff). I was disappointed in
> Mongo’s limitations for my use case. I wanted a separate Mongo database for
> each user, but the limit was too small. Also, the max database size was
> somewhat small. Anyhow, Soil looks to be what I would build (actually more
> than) if I had the time. Hope that helps.
>
> —
> Yanni Chiu
>
>
> On Thu, Apr 6, 2023 at 3:17 PM Charles Monteiro <
> [email protected]> wrote:
>
>> Assuming that Gemstone is already a candidate, although that case I would
>> be doing it thru a web interface which needed further development for my
>> purposes, what would people here do for persistence ?
>>
>> Plain old EXDI to an RDMS ?
>>
>> Glorp ?
>>
>> or the MongoDriver which I see has at least been updated to 4.4.8 ?
>>
>> from I"m using it from VW perspective what would be better i.e. for a
>> brand new app ?
>>
>> Any other suggestions?
>>
>> thanks
>>
>> --
>> Charles A. Monteiro
>>
>>

-- 
Charles A. Monteiro
https://urldefense.com/v3/__http://www.monteirosfusion.com__;!!DZ3fjg!8h-FjAymZAFP57J15DWeDzycJKUvC3d_9GgLPHnS20171FK2Cfb6KV5lhWJVq4taWBgOgRXDjbzpinf-12MONbcnrWBCz02ZHA$ 
sent from the road