These are chat archives for atomix/atomix

21st
Oct 2016
Jonathan Halterman
@jhalterman
Oct 21 2016 17:23
@dmvk Atomix is here to stay, but you are right about recent activity. I'd say we've just been busy with other work-related projects recently. Atomix is being used by us and others on internal projects, but its seems stable/mature enough to have not needed much attention lately. As for new feature development, there are lots of ideas, but no pressing timeline. We're certainly open to ideas and contributions though.
Jonathan Halterman
@jhalterman
Oct 21 2016 17:42
@digat Just start with the Getting Started guide and go from there through the docs: http://atomix.io/atomix/docs/getting-started/
Jonathan Halterman
@jhalterman
Oct 21 2016 17:50
@middlesphere I think it really comes down to your requirements around consistency. If you need all nodes to consistently, across nodes, see new session entries as they are created, changes as they're updated, and deletions as they're removed, in a way that avoids any potential conflict or races, then Atomix would be a good candidate. If the potential for conflict isn't a problem, then the strong consistency that Atomix provides probably isn't necessary.
In terms of storage scalability, what you're describing should be fine, either using in memory storage or on disk. The question is what your throughput requirements will be. Since each write to Atomix is replicated to (N / 2) + 1 nodes before it's considered successful, throughput obviously isn't as quick as for systems that are writing to a single node, such as if you were using Redis. But the tradeoff is that if/when a node goes down, all of your web sessions will remain in tact and available.
@middlesphere Since you're storing web sessions, you may also be interested in TTL for map entries: http://atomix.io/atomix/docs/collections/#expiring-keys
@txm119161336_twitter Snapshotting is optional, but yes it does require a bit of implementation on your part. Check out the example DistributedValue resource example which includes a snapshotting impl http://atomix.io/atomix/docs/custom-resources/
Also check out the Copycat docs on snapshots (which are a little different than Atomix, but cover the same general ideas): http://atomix.io/copycat/docs/state-machine/#state-machine-snapshots