Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of chirino@gmail.com designates
 72.14.220.153 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references:x-google-sender-auth;
        b=EQrIgn0lRZkFou9pF1ToS+/LNOpcy4t1yfmouZ6AVVtgNOAwUFcxTtf949rs11ENDA
         TDHbqUCdA4f3tXIUsT49XAAullyogrnUheWnKhgpPmrl9Htcy5OgVavRgYdo1CtSS3G0
         whXeTlJJRwzE5VXEKjsS1dk6OonrKTkUernKU=
Message-ID: <af2843cd0810021015r69d7dd9bn68ca35a7a4136c1b@mail.gmail.com>
Date: Thu, 2 Oct 2008 13:15:39 -0400
From: "Hiram Chirino" <hiram@hiramchirino.com>
Sender: chirino@gmail.com
To: dev@activemq.apache.org
Subject: Re: KahaDB Protocol Buffers and the future of ActiveMQ
In-Reply-To: <7b3355cb0810021001i1191bec1mc39a01fb9a28cd3b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <af2843cd0810020718r38b0e622yda5e95048b7c279e@mail.gmail.com>
	 <7b3355cb0810021001i1191bec1mc39a01fb9a28cd3b@mail.gmail.com>

On Thu, Oct 2, 2008 at 1:01 PM, Bruce Snyder <bruce.snyder@gmail.com> wrote:
> On Thu, Oct 2, 2008 at 8:18 AM, Hiram Chirino <hiram@hiramchirino.com> wrote:
>> Hi Guys,
>>
>> I've lately been working a new persistence store in the sandbox.  You
>> guys can check it out at:
>> https://svn.apache.org/repos/asf/activemq/sandbox/kahadb
>>
>> It's similar to the default AMQ store that is used by default today in
>> ActiveMQ 5.x, except that it fixes several short commings that we have
>> noticed in in the AMQ store.  This new store uses a transaction log,
>> but indexes the messages using BTrees which stay consistent on
>> restarts which means that store recovery times are very short even
>> when there are many messages stored in the database. This work is
>> approaching a stable point and I think that this should become the
>> default message store for ActiveMQ 6.0.  We need to start beating on
>> this to make sure it's rock solid.
>
> Are there any docs about how to hook this into, say, an ActiveMQ trunk
> build so we can start testing it now? I'd like to be able to configure
> it via the activemq.xml so I can switch back and forth.
>
>> While doing this bit of work, I decided to experiment with using
>> Google protocol buffers to encode the transaction log records and it
>> seems to have worked out well.  I think that we should
>> research/evaluate using protocol buffer based default wire format for
>> ActiveMQ.   In addition to being able to code generate marshallers for
>> many languages, I think we may get some substantial performance
>> improvements from using protocol buffers.  So I'm going to create a
>> new branch in the sandbox to experiment with changing out the
>> wireformat.  Hopefully, the performance gains do manifest themselves
>> and we can work on merging those changes back to trunk.
>
> Will the new store using Protocol Buffers be backwards compatible with
> with previous releases?
>

Well the new protocol will not be compatible, but I hope we can
support both protocols concurrently.

> Bruce
> --
> perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> Apache ActiveMQ - http://activemq.org/
> Apache Camel - http://activemq.org/camel/
> Apache ServiceMix - http://servicemix.org/
>
> Blog: http://bruceblog.org/
>


-- 
Regards,
Hiram

Blog: http://hiramchirino.com

Open Source SOA
http://open.iona.com