On 28 Jul 2014, at 11:36 , Esteban Lorenzano <estebanlm@gmail.com> wrote:
On 28 Jul 2014, at 11:15, Henrik Johansen <henrik.s.johansen@veloxit.no> wrote:
On 21 Jul 2014, at 3:34 , Esteban Lorenzano <estebanlm@gmail.com> wrote:
On 21 Jul 2014, at 09:44, stepharo <stepharo@free.fr> wrote:
On 21/7/14 08:46, Torsten Bergmann wrote:
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.
I was intending to add Riak support too :) Do you want access to the repo, so we keep all together? (and then I can check and maybe collaborate) and btw, are you using/checking Phriak?
Esteban
Sure, as you might have inferred from my mail, itâll probably be a bit before I start on the actual riak client, though itâs in my plans. First, Iâll need to finish up and release NBConverters (of which UTF8 conversion I want to use in PB implementation is a part), then Protobuffer implementation (data type serialization + message spec parsing), then parse in the Riak PB messages and build a client on top of that. And yes, Iâve checked Phriak, building a client on top of that would probably be much faster than what I intend. But, seeing as how thereâs 2.0 functionality exclusively implemented in the PB API, I thought itâd be nice to go the long route while Iâm at it. AFAICT, 2.0 mostly adds functionality, so it seems to me if someone wrote a backend using Phriak, a new client would be able to operate as a drop-in replacement if it is indeed more performant. (not to mention a nice starting point for a 2.0 backend which can utilize new functionality) Cheers, Henry