You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@thrift.apache.org by Ran Tavory <ra...@gmail.com> on 2010/05/03 11:16:18 UTC
RPC for java/python with rest support, HTML monitoring and goodies
Hi, I just posted this question on stackoverflow, I'd appreciate your
answer...
http://stackoverflow.com/questions/2757040/rpc-for-java-python-with-rest-support-html-monitoring-and-goodies
RPC for java/python with rest support, HTML monitoring and
goodies<http://questions/2757040/rpc-for-java-python-with-rest-support-html-monitoring-and-goodies>
Here's my set of requirements: I'm looking for an RPC framework such as
thrift, avro, protobuf (when adding services to it) which supports:
1. Easy and intuitive IDL. No serial numbers, no manual versioning,
simple... avro is a good example for this.
2. Works with Java and Python
3. Supports both fast binary prorocol, as well as HTTP based restful
style. I'd like to be able to use it for both backend-to-backend
communication (java-java or python-java) as well as frontend-to-backend
communication (javascript to java).
4. The rest support needs to include ¶m=value input as get/post
requests (configurable per request) and output in three possible formats:
json, jsonp, XML.
5. Compact, fast, backward compatible, easy to upgrade etc...
6. Provides some nice monitoring interfaces such as: JMX, web page status
reports (e.g. packets in, packets out, error rate etc)
7. Ops friendly... no need to take the whole site down to release new
versions
... other goodies are welcome...
Is there something out there?
So far I've looked at thrift and avro and they are both nice in some ways,
but don't check all my list.
Thanks
Re: RPC for java/python with rest support, HTML monitoring and
goodies
Posted by Bjørn Borud <bb...@gmail.com>.
On Mon, May 3, 2010 at 7:43 PM, Bryan Duxbury <br...@rapleaf.com> wrote:
>
> I created http://issues.apache.org/jira/browse/THRIFT-771 for adding JMX
> instrumentation. The web UI thing is a cool idea, but might be a little
> cumbersome as a default.
>
if the JMX stuff is in place then it shouldn't be too much work to offer a
monitoring servlet that the developer can choose to load in an embedded
webserver.
-Bjørn
Re: RPC for java/python with rest support, HTML monitoring and
goodies
Posted by Ran Tavory <ra...@gmail.com>.
thanks folks
On Mon, May 3, 2010 at 8:43 PM, Bryan Duxbury <br...@rapleaf.com> wrote:
> On Mon, May 3, 2010 at 2:16 AM, Ran Tavory <ra...@gmail.com> wrote:
>
> > 6. Provides some nice monitoring interfaces such as: JMX, web page
> status
> > reports (e.g. packets in, packets out, error rate etc)
> >
>
> I created http://issues.apache.org/jira/browse/THRIFT-771 for adding JMX
> instrumentation. The web UI thing is a cool idea, but might be a little
> cumbersome as a default.
>
Re: RPC for java/python with rest support, HTML monitoring and
goodies
Posted by Bryan Duxbury <br...@rapleaf.com>.
On Mon, May 3, 2010 at 2:16 AM, Ran Tavory <ra...@gmail.com> wrote:
> 6. Provides some nice monitoring interfaces such as: JMX, web page status
> reports (e.g. packets in, packets out, error rate etc)
>
I created http://issues.apache.org/jira/browse/THRIFT-771 for adding JMX
instrumentation. The web UI thing is a cool idea, but might be a little
cumbersome as a default.
Re: RPC for java/python with rest support, HTML monitoring and goodies
Posted by Bjorn Borud <bb...@gmail.com>.
Ran Tavory <ra...@gmail.com> writes:
>
> - Web form debugging
by this you mean having the option to perform RPC calls by filling in a
form in your browser? yeah, that is a surprisingly useful feature.
> the internal google rpc is nice, yes, but unfortunately only google has
> it...
from what I understand they would like to release it, but the problem is
that doing so would mean a lot of work and nobody has had the time to do
it. of course, the next best thing would be to st...er borrow some of
the good ideas.
the one thing I am missing the most from Thrift right now is some way to
associate credentials with a call in a way that doesn't get in a
developer's face. right now I have to add these things in-band and this
is inelegant. I mentioned that I might get some time to think about
this later this year, but I think there are people who want to, and are
able to, addres this earlier.
> I've seen a few public RPC frameworks based on protobuf but couldn't tell
> how ready they are.
well, I am an ex-googler and would naturally like to use protobuf, but I
chose Thrift, so that should probably tell you something about how ready
I feel the protobuf based RPC mechanisms are :-).
-Bjørn
Re: RPC for java/python with rest support, HTML monitoring and
goodies
Posted by Ran Tavory <ra...@gmail.com>.
2010/5/3 Bjørn Borud <bb...@gmail.com>
> On Mon, May 3, 2010 at 11:16 AM, Ran Tavory <ra...@gmail.com> wrote:
>
> > So far I've looked at thrift and avro and they are both nice in some
> ways,
> > but don't check all my list.
> >
>
> it might be very useful if you briefly summarized the top N things you feel
> lacks from Thrift.
>
- HTTP rest support (xml, json, jsonp)
- Web form debugging
- monitoring. performance during the last 5 min, 1 h etc, just like
google's... via a web monitoring form, plus JMX in java
- async calls (maybe it does have that - not sure...)
- Easy backward compatibility. Not actually sure how it works in thrift -
can I remove fields? Can I add them only at the end? Do I have to manually
manage version numbers and field numbers? I think in that sense avro claims
to be better.
>
> (I regularly pester people at Google to get them to release their own RPC
> mechanism built on protobuf, but it doesn't look like I've been able to
> provoke enough interest. I happen to like the RPC mechanism used in Google
> quite a lot, but for now I am using Thrift).
>
the internal google rpc is nice, yes, but unfortunately only google has
it...
I've seen a few public RPC frameworks based on protobuf but couldn't tell
how ready they are.
>
> -Bjørn
> --
> Bjørn Borud <bb...@gmail.com>
> +47 920 46465
>
Re: RPC for java/python with rest support, HTML monitoring and
goodies
Posted by Bjørn Borud <bb...@gmail.com>.
On Mon, May 3, 2010 at 11:16 AM, Ran Tavory <ra...@gmail.com> wrote:
> So far I've looked at thrift and avro and they are both nice in some ways,
> but don't check all my list.
>
it might be very useful if you briefly summarized the top N things you feel
lacks from Thrift.
(I regularly pester people at Google to get them to release their own RPC
mechanism built on protobuf, but it doesn't look like I've been able to
provoke enough interest. I happen to like the RPC mechanism used in Google
quite a lot, but for now I am using Thrift).
-Bjørn
--
Bjørn Borud <bb...@gmail.com>
+47 920 46465