Am 28.07.2014 um 11:15 schrieb Henrik Johansen <[email protected]>:
> > On 21 Jul 2014, at 3:34 , Esteban Lorenzano <[email protected]> wrote: > >> >> On 21 Jul 2014, at 09:44, stepharo <[email protected]> wrote: >> >>> >>> On 21/7/14 08:46, Torsten Bergmann wrote: >>>> DALI >>>> http://ss3.gemstone.com/ss/DALi.html >>>> >>>> VOYAGE >>>> http://smalltalkhub.com/#!/~estebanlm/Voyage >>> >>> I do not know if there are back ends for something else than mongo in >>> Voyage. >> >> certainly not for GOODS :) >> actually we have just “in memory” and “mongo” (in memory works fine when >> deploying on gemstone, for example) >> I always want to add more backends but well… time, time, time… >> >> Esteban > > I’m intending to add one for Riak, in an unspecified amount of time, > depending on my other workload… > I’d like it performant, and use a client up to date with the latest Riak API, > which (afaict) means using the ProtoBuffer protocol, which means having to > implementing PB first. > The progress so far is I got the PB serializer almost done (sidetracked by > wanting an NB-based UTF8 converter to make it more performant), but I haven’t > started the PB message parser yet, nor the actual Riak backend. > Isn't there an implementation from Göran Krampe for ProtoBuf? Maybe that is already complete in some sense. Having a Riak backend for voyage would be great. But then there should be some notion to control indices, right? In MongoTalk and Voyage there is nothing like an index. For Mongo indices are separate from the data. In Riak they are not (really) because I think it only works performant if secondary indices are written (being meta/header data) when the data is written. Any opinion on this? Norbert
