I am also asking myself the same questions. But there are ways to achieve it all with Pharo I think. It may require more shuffling of data but it can be done.
Especially when looking at the problems with uncoupling the parts (like I do here w/ RabbitMQ and Stamp). Much easier to use services (returning json or Ston (better)) to load user views on data. Not as nice as pure OO everywhere but still very productive. Phil On Wed, Oct 2, 2013 at 9:42 PM, Sven Van Caekenberghe <[email protected]> wrote: > Mariano, > > On 02 Oct 2013, at 20:49, Mariano Martinez Peck <[email protected]> > wrote: > > > Hi guys. > > First, let me apologize for the amount of emails I am sending. I am > doing an analysis to see if GemStone is a good candidate for a project I am > working and so it deserves some research. > > > > I wondered if any has ever tried porting any of these tools to GemStone: > Fuel, Glorp, Native PostgreSQL driver, Voyage and MongoDB. > > I do not understand. > > IMHO there is only one reason to go to Gemstone, and that is to use its > capabilities as OODB. All the technologies you mention are persistency > related and would not be needed in that case, right ? > > As you most probably know, you can get pretty far with Pharo. After that, > there is load-balancing, partitioning, message queues. Pretty much what any > technology stack does. > > You will always find more tools and libraries on the Pharo side, as the > community is much larger. > > Sven > > > Thanks a lot in advance, > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > >
