Careful, HawtDB is deprecated, as advertised in the camel-hawtdb component page. Unfortunately, the warning doesn't render in a shaded box any longer (due to some recent Confluence migration), so it's easy to miss it. Sorry about that.
LevelDB is recommended instead, but the technology has two limitation: it runs embedded and only one physical process can open the data files simultaneously. In other words, it does not support distributed access OOTB. The old-school advice would be to use the JDBC Aggregation Repository along with either a SQL DB or a NoSQL DB from whom JDBC support exists. For example, there are some experimental projects providing JDBC drivers for MongoDB, or OrientDB has some support for JDBC too. Alternatively, we would be extremely happy if you contributed a new NoSQL Aggregation Repository. I can see much benefit in incorporating a MongoDB Aggregation Repository to the camel-mongodb component which uses the native Java driver. Regards, *Raúl Kripalani* Apache Camel PMC Member & Committer | Enterprise Architect, Open Source Integration specialist http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani http://blog.raulkr.net | twitter: @raulvk On Wed, Jan 8, 2014 at 3:14 PM, Tom Fornoville <tom.fornovi...@roots.be>wrote: > Hi camel-users, > > Since we're going to run our system distributed (multiple containers in > Fuse Fabric) we need an alternative to the default > MemoryAggregationRepository. > > Although we found it awkward that the Hazelcast component only offers an > IdempotentRepository and no AggregationRepository we found an > implementation here: https://github.com/smecsia/camel-hazelcast. We tried > that but sometimes we get strange TimeoutExceptions and we're not > experienced enough with Hazelcast to determine the root-cause. > > Some extra searching on the Camel site led me to HawtDB ( > http://camel.apache.org/hawtdb.html). > So I now have 3 questions: > 1) does HawtDB work out-of-the-box in a distributed environment (provided > that you can place the file on a shared location), and can it recover > wihtout extra manual steps? > > 2) can you place multiple repositories in a single file or do you need a > separate file per repository (we have 5 aggregators on our system, each one > needing its own repository) > > 3) are there any other proven and documented implementations of > AggregationRepository that work in distributed environments? > > Thanks in advance, > Tom >
