Return-Path: Delivered-To: apmail-avro-user-archive@www.apache.org Received: (qmail 63662 invoked from network); 19 Jul 2010 19:19:28 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 19 Jul 2010 19:19:28 -0000 Received: (qmail 19160 invoked by uid 500); 19 Jul 2010 19:19:28 -0000 Delivered-To: apmail-avro-user-archive@avro.apache.org Received: (qmail 19079 invoked by uid 500); 19 Jul 2010 19:19:28 -0000 Mailing-List: contact user-help@avro.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@avro.apache.org Delivered-To: mailing list user@avro.apache.org Received: (qmail 19068 invoked by uid 99); 19 Jul 2010 19:19:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Jul 2010 19:19:28 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rantav@gmail.com designates 209.85.161.43 as permitted sender) Received: from [209.85.161.43] (HELO mail-fx0-f43.google.com) (209.85.161.43) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Jul 2010 19:19:20 +0000 Received: by fxm18 with SMTP id 18so2259296fxm.30 for ; Mon, 19 Jul 2010 12:19:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type; bh=xGEUthX4hXvsRLNrJjfW/QrlysrM1AsGqpvsKQpjvQo=; b=Nlw6yMR+BXnyDk9cP3DX18+khjGYuLowxMoMNVjNEkfSgwqm7MbnFDKF+xKCtP6OI4 912wSlCjW/WQN8t3WlFR3ve6EX4lzXrRxUIEpm6Gv9q5miyCOvWOYAnHRS7Jj4N1Ikor sjfER7FAuMX9GeRuC1VMB1V1ZV6QRMYUXZ11w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=DlIeGsI7cz/NxWSiApoa0wtxlymtha4xRlPXAXH6vLyDZXJolHk0mnBpvhY+rKLhTe XmOXrN0lRjJJnpzbCE+54mkF4oKDkfhzpACmMvYbdhEsb1uQb/VDDb7qxyjNezd89meg BJu+j1/xKJ0yhUSL4woDkMxQuf2MDfQXL0rao= Received: by 10.239.132.212 with SMTP id 20mr383825hbs.206.1279567140175; Mon, 19 Jul 2010 12:19:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.239.159.4 with HTTP; Mon, 19 Jul 2010 12:18:40 -0700 (PDT) In-Reply-To: <4C44A2E6.7040508@apache.org> References: <4C44A2E6.7040508@apache.org> From: Ran Tavory Date: Mon, 19 Jul 2010 22:18:40 +0300 Message-ID: Subject: Re: is avro production ready? To: user@avro.apache.org Content-Type: multipart/alternative; boundary=001485f44c52db4338048bc270ac X-Virus-Checked: Checked by ClamAV on apache.org --001485f44c52db4338048bc270ac Content-Type: text/plain; charset=UTF-8 On Mon, Jul 19, 2010 at 10:09 PM, Doug Cutting wrote: > On 07/19/2010 11:43 AM, Ran Tavory wrote: > >> I'd like to use avro in several use cases: >> 1. RPC. Both using json over HTTP and binary over TCP (will use both >> modes). Async RPC clients/servers isn't a showstopper but could also be >> nice >> > > Binary RPC over HTTP is the supported mode today. We'd eventually like to > standardize on a second, non-HTTP, TCP-based high-performance, async, > secure, RPC transport. There are some TCP-based transports implemented that > support request-only messages and async i/o, but these are non-standard and > might not provide a good basis for long-term interoperability. > > I'd really like to have json over HTTP as well, even if not as the core service transport (binary over http is fine), then at least for debugging a remote service. So it doesn't have to be performant, just work, is there something ready? (I guess I can write a silly one myself...) > > 2. As a serialization mechanism to send messages over AMQ or save object >> on memcached >> > > This should work well today. > > > 3. Perhaps use for saving space in logs (rather than plain text log >> files) and in combination with flume. I haven't thought that out yet. >> > > Log files are a good use of Avro today. Avro 1.4.0 will be released soon > and contains APIs to write MapReduce programs that process Avro data files. > Support for Avro in Flume is expected soon. > > Doug > --001485f44c52db4338048bc270ac Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Mon, Jul 19, 2010 at= 10:09 PM, Doug Cutting <cutting@apache.org> wrote:
On 07/19/2010 11:43 AM, Ran Tavory wrote:
I'd like to use avro in several use cases:
1. RPC. Both using json over HTTP and binary over TCP (will use both
modes). Async RPC clients/servers isn't a showstopper but could also be= nice

Binary RPC over HTTP is the supported mode today. =C2=A0We'd eventually= like to standardize on a second, non-HTTP, TCP-based high-performance, asy= nc, secure, RPC transport. =C2=A0There are some TCP-based transports implem= ented that support request-only messages and async i/o, but these are non-s= tandard and might not provide a good basis for long-term interoperability.<= div class=3D"im">
I'd really like to have json over HTTP as w= ell, even if not as the core service transport (binary over http is fine), = then at least for debugging a remote service. So it doesn't have to be = performant, just work, is there something ready? (I guess I can write a sil= ly one myself...)

2. As a serialization mechanism to send messages over AMQ or save object on memcached

This should work well today.


3. Perhaps use for saving space in logs (rather than plain text log
files) and in combination with flume. I haven't thought that out yet.

Log files are a good use of Avro today. =C2=A0Avro 1.4.0 will be released s= oon and contains APIs to write MapReduce programs that process Avro data fi= les. =C2=A0Support for Avro in Flume is expected soon.

Doug

--001485f44c52db4338048bc270ac--