Thanks John, very interesting reading.
No luck for us in inventory, as there's essentially updates rather than
inserts, which is a bit more complicated than the solution described:
"generally
the client needs to be smart enough to merge updates based on a timestamp,
with a periodic batch job that cleans out obsolete inserts"
But now we're considering the alternative of reading/writing the whole
graph at once and process queries in memory. If "the whole graph" is too
big to fit in memory without problems, then we should find a way to
partition it.
On Sat, Dec 17, 2016 at 2:54 AM, John Sanda <jsanda(a)redhat.com> wrote:
This thread post
https://goo.gl/8cpSwM from cassandra-users list has
a
good write up on an approach for implementing transactions across multiple
tables in order to provide stronger consistency. I found it particularly
interesting in light of the discussions of inventory and consistency.
- John
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev