4 ms·

Having used HazelCast extensively, and considering making some of my code Sirius-depentant, I can tell you that it is not more advanced. Sirius is basically jus

by larsmak 12y ago

Having used HazelCast extensively, and considering making some of my code Sirius-depentant, I can tell you that it is not more advanced. Sirius is basically just a distributed key-value store w/no partitioning, whereas HazelCast has a lot of abstractions built on top of the simpler principle[1]. In fact, it might be a bit overkill in some situations, and that's one of the reasons I will consider Sirius. [1] http://www.hazelcast.org/docs/3.1/manual/html-single/ http://www.hazelcast.org/docs/3.1/manual/html-single/

bri3d 12y ago
Good point! I agree and I think we were looking at different dimensions: the consistency/partition tolerance story (the "distributed system" bits) seem more thought out in Sirius while the variety of data structures and connectors look more built up in HazelCast. This may be an issue of documentation as well: Because it's built more "vertically" with a large consumer-facing cross-section (lots of data structures stacked over each other), the HazelCast documentation seems to be very use-oriented while the Sirius documentation focuses on the fundamentals.
- agibsonccc 12y ago
  Yeah, I definitely use hazelcast for the variety of data structures. I personally use it for a variety of tasks including distributed locks, a task tracker (think like hadoop) and for phases. If you're curious, here's the impl I'm talking about: https://github.com/agibsonccc/java-deeplearning/blob/master/deeplearning4j-scaleout/deeplearning4j-scaleout-akka/src/main/java/org/deeplearning4j/iterativereduce/tracker/statetracker/hazelcast/HazelCastStateTracker.java https://github.com/agibsonccc/java-deeplearning/blob/master/... This is to augment an akka clustering distributed run time.
comcast-jonm 12y ago
Our particular reference dataset (TV and movie data) had some application use cases that required custom data structures to get the in-memory performance we wanted. Sirius doesn't provide datastructures per se (and isn't really even a datastore itself)--it provides an eventually-consistent, replicated update stream that you can use to maintain your own datastructures. Having that developer freedom and control over the datastructures was an important design principle.
- sk8r00 12y ago
  Did your design principle make it so as I type this 75% of Comast customers are reporting internet problems, 18% are having problems with cable tv and 5% are on total black out and have been for at least the past three days. Go check is it down. Comcast is almost always down in some way. Again in the time it's taken me to type this my cable has gone out and come back intermittently 5 times. This is ridiculous.

by larsmak 12y ago

bri3d 12y ago

Good point! I agree and I think we were looking at different dimensions: the consistency/partition tolerance story (the "distributed system" bits) seem more thought out in Sirius while the variety of data structures and connectors look more built up in HazelCast. This may be an issue of documentation as well: Because it's built more "vertically" with a large consumer-facing cross-section (lots of data structures stacked over each other), the HazelCast documentation seems to be very use-oriented while the Sirius documentation focuses on the fundamentals.

agibsonccc 12y ago
Yeah, I definitely use hazelcast for the variety of data structures. I personally use it for a variety of tasks including distributed locks, a task tracker (think like hadoop) and for phases. If you're curious, here's the impl I'm talking about: https://github.com/agibsonccc/java-deeplearning/blob/master/deeplearning4j-scaleout/deeplearning4j-scaleout-akka/src/main/java/org/deeplearning4j/iterativereduce/tracker/statetracker/hazelcast/HazelCastStateTracker.java https://github.com/agibsonccc/java-deeplearning/blob/master/... This is to augment an akka clustering distributed run time.

comcast-jonm 12y ago

Our particular reference dataset (TV and movie data) had some application use cases that required custom data structures to get the in-memory performance we wanted. Sirius doesn't provide datastructures per se (and isn't really even a datastore itself)--it provides an eventually-consistent, replicated update stream that you can use to maintain your own datastructures. Having that developer freedom and control over the datastructures was an important design principle.

sk8r00 12y ago
Did your design principle make it so as I type this 75% of Comast customers are reporting internet problems, 18% are having problems with cable tv and 5% are on total black out and have been for at least the past three days. Go check is it down. Comcast is almost always down in some way. Again in the time it's taken me to type this my cable has gone out and come back intermittently 5 times. This is ridiculous.