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 >
