No, I don't think I'm storing anything specific to Pharo... just model objects.
We're handling quite a lot of user of data right now, so migration is a must, any ideas? :P Thanks! Bernat. 2013/1/29 Martin Dias <[email protected]> > I don't know of any port of Fuel to Gemstone. The difficulty depends > on what objects you have serialized. You don't store too specific > stuff, like block closures or classes, right? > > Cheers, > Martin > > On Tue, Jan 29, 2013 at 4:14 PM, Bernat Romagosa > <[email protected]> wrote: > > I see, thanks for the answers! > > > > What about moving all the data to the new Gemstone configuration? Is it > > possible to materialize Fuel graphs from within Gemstone? > > > > > > 2013/1/29 Paul DeBruicker <[email protected]> > >> > >> I'm sure the gemstone guys will chime in with more details. > >> > >> Iliad does not have to run in the GemTools image. No need to get > 0.9.1.2 > >> to run in older Pharo versions. You just use the GemTools image as the > IDE > >> for Gemstone. So start the GemTools image and connect to the stone and > use > >> it to load Iliad 0.9.1.2 into Gemstone by running the Gemstone specific > >> Monticelo or workspace or browsers. > >> > >> > >> > >> > >> > >> On Jan 29, 2013, at 5:22 AM, Bernat Romagosa > >> <[email protected]> wrote: > >> > >> > Hi list, > >> > > >> > I've heard the "develop in Pharo, deploy in Gemstone" idea a million > >> > times, and I'd like to understand how people proceed in real-world > cases. > >> > > >> > I've done my homework and I've watched and read a lot of beginner > >> > tutorials, but I still have lots of pieces missing. Here's our > scenario: > >> > > >> > We have a web app, built on Pharo 1.4 and Iliad 0.9.1.2. Currently, we > >> > handle persistence on the image and we have a scheduler process doing > >> > regular Fuel backups every 10 minutes, and we also keep daily backups > in > >> > case things go wrong. > >> > > >> > The app is starting to gain momentum, and it feels like things are > going > >> > to start being way too sluggish soon, so we need to scale. > >> > > >> > We've been trying many different persistence approaches, but we'd love > >> > to stay inside Smalltalk. We hate having to flatten and pump back our > >> > objects all the time. Also, REST apis to any kind of DB are not good > enough > >> > for us, every o(n) operation becomes unbearably slow, as n REST calls > must > >> > be sent out and n answers received. > >> > > >> > In short, we want to use Gemstone, as we've read it's best for > complex, > >> > intertwined Smalltalk models, and it scales like crazy. > >> > > >> > We'd be okay with Pharo being the "dealer" between clients and the DB, > >> > but as I understand, GemTools can't be installed on Pharo 1.4, so > we're kind > >> > of stuck with an old Pharo 1.1.1 image, in which Iliad 0.9.1.2 can't > be > >> > installed. > >> > > >> > What's the solution here? How does one proceed to migrate an app of > this > >> > kind? We've developed in Pharo, now how does one accomplish the > "deploy in > >> > Gemstone" part? > >> > > >> > Any pointers to documentation, blog posts or whatever will be so much > >> > appreciated. > >> > > >> > Thanks a lot in advance, > >> > > >> > Bernat. > >> > > >> > -- > >> > Bernat Romagosa. > >> > > > > > > > > -- > > Bernat Romagosa. > > -- Bernat Romagosa.
