Proposal: RESTful coordinator service for the Voldemort cluster - project-voldemort

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Proposal: RESTful coordinator service for the Voldemort cluster
Received-SPF: pass (google.com: domain of maarten.koopm...@gmail.com designates 209.85.210.180 as permitted sender) client-ip=209.85.210.180;
MIME-Version: 1.0
In-Reply-To: <0600a354-46cb-4a4f-b7a7-d0612b38d292@googlegroups.com>
References: <2f5a22df-8ab1-49a6-a9f7-3cbd5e6c0042@googlegroups.com>
	<CA+O4ak4x1J6rU1vOnMgkVQmUzz9NuJYEiw-wNKH13u9wsAd...@mail.gmail.com>
	<CAJ9WAGfEZum9tWFF+KZDTfuv7aKPzuZG0j7R3dTeTGJEAsg...@mail.gmail.com>
	<0600a354-46cb-4a4f-b7a7-d0612b38d292@googlegroups.com>
Date: Wed, 17 Oct 2012 07:37:22 +0200
Message-ID: <CAJ9WAGfwKCFon_TbFj6CXT4ny8=F-vMunNZvONkeKDxVkF0...@mail.gmail.com>
Subject: Re: [project-voldemort] Proposal: RESTful coordinator service for the
 Voldemort cluster
From: Maarten Koopmans <maarten.koopm...@gmail.com>
To: "project-voldemort@googlegroups.com" <project-voldemort@googlegroups.com>
Content-Type: multipart/alternative; boundary=e89a8f2358232e9c4104cc3aaa59

--e89a8f2358232e9c4104cc3aaa59
Content-Type: text/plain; charset=ISO-8859-1

Sounds like were thinking along the same lines. I'm on it, I'll update with
a status within a week.

Contact me if you want to discuss this.

--Maarten

On Tuesday, October 16, 2012, Chinmay Soman wrote:

>
> Currently, we're thinking of using Netty for implementing the REST enabled
> coordinator and make that part open source. The other component is
> essentially a software load balancer with a persistent HTTP connection pool
> which is the core of the thin client. This thin client will be released
> internal to LinkedIn at first.
>
> But yes, any good load balancing solution (along with a HTTP connection
> pool) will work in this case. I agree that wont be a lot of work: anyone
> willing to take this up ?
>
> I'm currently designing the REST API for the coordinator. Since we dont
> want to do any extra work, the de-compression, de-serialization and
> inconsistency resolver modules should still be located in the thin client.
> This means we can only transfer raw bytes between the thin client and the
> coordinator. In my prototype I'm going to use base64 encoding to send the
> data to and fro. But are there any specific suggestions with respect to the
> REST API ?
>
> Lemme know,
> C
>
> On Monday, October 15, 2012 2:51:24 AM UTC-7, maarten wrote:
>>
>> Sounds nice, I have been toying with the idea of putting a REST proxy
>> for a Voldemort cluster. The elephant in the room is of course how to
>> shield the resources - i.e. add session management/authN or not.
>>
>> Using Lift/Scala it should be a few days of work. What is your planning?
>>
>> --Maarten
>>
>> On Thu, Oct 11, 2012 at 1:41 PM, Sunny Gleason <sunny....@gmail.com>
>> wrote:
>> > On 10/11/12, Chinmay Soman <chinmay...@gmail.com> wrote:
>> >> At LinkedIn, there is a *proprietary solution* that resolves the above
>> Open
>> >> Issue. Unfortunately, the proprietary solution is not open sourced
>> (yet).
>> >> So we're opening this question to the community: What open source
>> options
>> >> may resolve our *Open Issue*?
>> >
>> > You should check out Riak.
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups "project-voldemort" group.
>> > To unsubscribe from this group, send email to project-voldem...@**
>> googlegroups.com.
>> > Visit this group at http://groups.google.com/**
>> group/project-voldemort?hl=en<http://groups.google.com/group/project-voldemort?hl=en>.
>>
>> >
>> >
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "project-voldemort" group.
> To unsubscribe from this group, send email to
> project-voldemort+unsubscribe@googlegroups.com <javascript:_e({}, 'cvml',
> 'project-voldemort%2Bunsubscribe@googlegroups.com');>.
> Visit this group at http://groups.google.com/group/project-voldemort?hl=en
> .
>
>
>

--e89a8f2358232e9c4104cc3aaa59
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Sounds like were thinking along the same lines. I&#39;m on it, I&#39;ll upd=
ate with a status within a week.<div><br></div><div>Contact me if you want =
to discuss this.</div><div><br></div><div>--Maarten<span></span><br><br>
On Tuesday, October 16, 2012, Chinmay Soman  wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex"><div><br></div>Currently, we&#39;re thinking of using Netty for =
implementing the REST enabled coordinator and make that part open source. T=
he other component is essentially a software load balancer with a persisten=
t HTTP connection pool which is the core of the thin client. This thin clie=
nt will be released internal to LinkedIn at first.=A0<div>
<br></div><div>But yes, any good load balancing solution (along with a HTTP=
 connection pool) will work in this case. I agree that wont be a lot of wor=
k: anyone willing to take this up ?</div><div><br></div><div>I&#39;m curren=
tly designing the REST API for the coordinator. Since we dont want to do an=
y extra work, the de-compression, de-serialization and inconsistency resolv=
er modules should still be located in the thin client. This means we can on=
ly transfer raw bytes between the thin client and the coordinator. In my pr=
ototype I&#39;m going to use base64 encoding to send the data to and fro. B=
ut are there any specific suggestions with respect to the REST API ?</div>
<div><br></div><div>Lemme know,</div><div>C</div><div><br>On Monday, Octobe=
r 15, 2012 2:51:24 AM UTC-7, maarten wrote:<blockquote class=3D"gmail_quote=
" style=3D"margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">
Sounds nice, I have been toying with the idea of putting a REST proxy
<br>for a Voldemort cluster. The elephant in the room is of course how to
<br>shield the resources - i.e. add session management/authN or not.
<br>
<br>Using Lift/Scala it should be a few days of work. What is your planning=
?
<br>
<br>--Maarten
<br>
<br>On Thu, Oct 11, 2012 at 1:41 PM, Sunny Gleason &lt;<a>sunny....@gmail.c=
om</a>&gt; wrote:
<br>&gt; On 10/11/12, Chinmay Soman &lt;<a>chinmay...@gmail.com</a>&gt; wro=
te:
<br>&gt;&gt; At LinkedIn, there is a *proprietary solution* that resolves t=
he above Open
<br>&gt;&gt; Issue. Unfortunately, the proprietary solution is not open sou=
rced (yet).
<br>&gt;&gt; So we&#39;re opening this question to the community: What open=
 source options
<br>&gt;&gt; may resolve our *Open Issue*?
<br>&gt;
<br>&gt; You should check out Riak.
<br>&gt;
<br>&gt; --
<br>&gt; You received this message because you are subscribed to the Google=
 Groups &quot;project-voldemort&quot; group.
<br>&gt; To unsubscribe from this group, send email to <a>project-voldem...=
@<u></u>googlegroups.com</a>.
<br>&gt; Visit this group at <a href=3D"http://groups.google.com/group/proj=
ect-voldemort?hl=3Den" target=3D"_blank">http://groups.google.com/<u></u>gr=
oup/project-voldemort?hl=3Den</a>.
<br>&gt;
<br>&gt;
<br></blockquote></div>

<p></p>

-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;project-voldemort&quot; group.<br>
To unsubscribe from this group, send email to <a href=3D"javascript:_e({}, =
&#39;cvml&#39;, &#39;project-voldemort%2Bunsubscribe@googlegroups.com&#39;)=
;" target=3D"_blank">project-voldemort+unsubscribe@googlegroups.com</a>.<br=
>

Visit this group at <a href=3D"http://groups.google.com/group/project-volde=
mort?hl=3Den" target=3D"_blank">http://groups.google.com/group/project-vold=
emort?hl=3Den</a>.<br>
=A0<br>
=A0<br>
</blockquote></div>

--e89a8f2358232e9c4104cc3aaa59--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
