How to best store arbitrarily large Java objects

Henning Verbeek hankipanky at
Fri Jul 22 04:12:59 EDT 2016

thanks for the very quick response.

On Thu, Jul 21, 2016 at 5:36 PM, Alex Moore <amoore at> wrote:
>> I'm beginning to think that I'll need to remodel my data and use CRDTs
>> for individual fields such as the `TreeMap`. Would that be a better
>> way?
> This sounds like a plausible idea.  If you do a lot of possibly conflicting
> updates to the Tree, then a CRDT map would be the way to go.  You could
> reuse the key from the main object, and just put it in the new
> buckettype/bucket.

Looking at the [documentation](
I assume there are no limits to the amount of entries, right?

> If you don't need to update the tree much, you could also just serialize the
> tree into it's own object - split up the static data and the often updated
> data, and put them in different buckets that share the same key.

The tree is built once and read often, rarely appended to. The problem
with splitting up the object is that the tree makes up about 95% of
the size, so unless I can split up the tree, it wont help much.

Thanks again!

PS: It'd be great to have a `Converter` that can be instructed to map
fields to CRDT through annotations :)

My other signature is a regular expression.

More information about the riak-users mailing list