Re: How to best store arbitrarily large Java objects

On 22 Jul 2016, at 09:12, Henning Verbeek wrote: > Alex, > thanks for the very quick response. > > On Thu, Jul 21, 2016 at 5:36 PM, Alex Moore wrote: >>> I'm beginning to think that I'll need to remodel my data and use CRDTs >>> for individual fields

Re: How to best store arbitrarily large Java objects

Alex, thanks for the very quick response. On Thu, Jul 21, 2016 at 5:36 PM, Alex Moore 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

Re: How to best store arbitrarily large Java objects

Hi Henning, Responses inline: ... > However, depending on the size of the `TreeMap`, the serialization > output can become rather large, and this limits the usefulness of my > object. In our tests, dealing with Riak-objects >2MB proved to be > significantly slower than dealing with objects

How to best store arbitrarily large Java objects

I have a Java class, which is being stored in Riak. The class contains a `TreeMap` field, amongst other fields. Out of the box, Riak is converting the object to/from JSON. Everything works fine. However, depending on the size of the `TreeMap`, the serialization output can become rather large, and