DALI http://ss3.gemstone.com/ss/DALi.html VOYAGE http://smalltalkhub.com/#!/~estebanlm/Voyage Any experiences to share about pro and cons? Thanks T.
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.
Any experiences to share about pro and cons?
Thanks T.
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
Any experiences to share about pro and cons?
Thanks T.
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. Cheers, Henry
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
Cheers, Henry
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.
It would be good to have a ProtoBuffers implementation that is separate. The same goes for the BSON implementation hidden in StHub.
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
Cheers, Henry
Am 28.07.2014 um 11:41 schrieb Sven Van Caekenberghe <sven@stfx.eu>:
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.
It would be good to have a ProtoBuffers implementation that is separate. The same goes for the BSON implementation hidden in StHub.
The BSON code should be loadable without MongoTalk. It is separate packages. Or do you mean a separate repository would be better? IMHO it would be sufficient to find it but smalltalkhub isn't helpful in this respect. Norbert
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
Cheers, Henry
On 28 Jul 2014, at 11:45, Norbert Hartl <norbert@hartl.name> wrote:
Am 28.07.2014 um 11:41 schrieb Sven Van Caekenberghe <sven@stfx.eu>:
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.
It would be good to have a ProtoBuffers implementation that is separate. The same goes for the BSON implementation hidden in StHub.
The BSON code should be loadable without MongoTalk. It is separate packages. Or do you mean a separate repository would be better?
With separate I mean: being managed, documented, advertised, tested and used as such, it is more a mindset than how this is exactly done. Someone needs it for something new, point them to the right place and they are off. Protocols are (should be) ideal building blocks. But it _is_ more work than having it as a local subpart of some larger project.
IMHO it would be sufficient to find it but smalltalkhub isn't helpful in this respect.
Norbert
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
Cheers, Henry
Am 28.07.2014 um 11:51 schrieb Sven Van Caekenberghe <sven@stfx.eu>:
But it _is_ more work than having it as a local subpart of some larger project.
Slightly ;) Who does not properly package and document his own stuff? Wait â¦. the original author seems to be a Kent Beck. Anyone knows him? :) Norbert
On 28 Jul 2014, at 11:41 , Sven Van Caekenberghe <sven@stfx.eu> wrote:
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.
It would be good to have a ProtoBuffers implementation that is separate.
I agree, keeping the building blocks separate is nice :) Cheers. Henry
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
Am 28.07.2014 um 11:15 schrieb Henrik Johansen <henrik.s.johansen@veloxit.no>:
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.
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
participants (7)
-
Esteban Lorenzano -
Henrik Johansen -
Norbert Hartl -
Sebastian Sastre -
stepharo -
Sven Van Caekenberghe -
Torsten Bergmann