I think Voyage with its connection to Mongo is somewhat more palatable to some companies - however I did forget to mention Glorp of course - which does map directly to a SQL database.
Not to dis Gemstone in anyway (I do wish OO db's had gained more traction in the past, they are still glorious) - and I do think they might have solutions to map to a SQL db to appease corp teams - although I'm not sure. Again - I think its useful to understand the patterns at play and how we can help folks understand where/how to play. Tim On Sun, 18 Feb 2024, at 10:40 PM, Yanni Chiu wrote: > Agreed that larger orgs and BI teams likely slant toward SQL. But GemStone > and Voyage/Mongo wouldn’t address that either. An export from a Soil, > GemStone or Mongo db, into a SQL db should address the BI tools. > > On Sun, Feb 18, 2024 at 4:35 PM Tim Mackinnon <tim@testit.works> wrote: >> __ >> I wasn't particularly advocating any path - but have observed that in larger >> orgs its a more difficult discussion to tread a different path (rightly or >> wrongly) - you have to cope with BI teams, who know mainly SQL based tools >> and equivalently support teams who know the same - and if in that world you >> may have to play their game (or not - if you have traction). So I'm just >> observing that we can work in any of those spaces - you can take your pick >> and apply what makes sense in your environment. >> >> Of course I love a rebel technology as much as anyone else - but sometimes >> their are other battles to fight - or more interesting niches to explore. >> >> >> Tim >> >> On Sun, 18 Feb 2024, at 5:06 PM, Yanni Chiu wrote: >>> Tim, >>> >>> What is the thinking behind “Finally you might need something more >>> enterprise and then Gemstone or Voyage…”? >>> >>> Is it the maturity level of Soil codebase vs. these others? Or is it a >>> belief that a database has to be a complex separate piece of engineering >>> (therefore best outsourced). >>> >>> Yanni >>> >>> On Sun, Feb 18, 2024 at 11:02 AM Tim Mackinnon <tim@testit.works> wrote: >>>> __ >>>> I think Ross (and what Norbert said) nicely alludes to the path people >>>> follow - for really simple persistence, Fuel or simple image saving give >>>> you an instant solution. The next step (assuming no real concurrency >>>> issues) are what Sean has maintained - something that gives you rolling >>>> snapshots and a simple UI/mechanism to recover old versions and then you >>>> probably realise that you need something more transactional and Soil >>>> sounds like it fits that perfectly. Finally you might need something more >>>> enterprise and then Gemstone or Voyage are the direction to travel. >>>> >>>> Having so many options is terrific particularly if you can defer some of >>>> the complexity the latter stages bring. I love it. >>>> >>>> Thanks for everyone for giving us so many options. >>>> >>>> Tim >>
