What are the advantages and disadvantages of Chronicle Map over Hazelcast?

[dk.h...@gmail.com]

I might be wrong but it looks like Hazelcast has better clustering / fail-over support while Chronicle Map might be faster.

Can anyone help to list in what areas one would be better or worse than the other one?

Thanks,

-DK

[Roman Leventov]

Most obvious thing is that Hazelcast's off-heap high density store is closed source and cost money: https://hazelcast.com/use-cases/caching/high-density-caching/. In Chronicle Map off-heap store is the only type store (however, Chronicle Engine allows on-heap stores as pluggable replacements of Chronicle Map). Also, Chronicle Map allows to persist data to disk and concurrent inter-process access to the same store, not sure if Hazelcast's off-heap store has such features.

You can read a short but comprehensive summary of Chronicle Map features here: https://github.com/OpenHFT/Chronicle-Map#3-min-to-understand-everything-about-chronicle-map

Replication / clustering / failover is implemented via Chronicle Engine and Chronicle Enterprise, these products have different model from Hazelcast IMDG and I think it's better to compare them for a particular use-case, not generally.

--
You received this message because you are subscribed to the Google Groups "Chronicle" group.
To unsubscribe from this group and stop receiving emails from it, send an email to java-chronicl...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[dk.h...@gmail.com]

Thanks, Roman. Do you know the status of the battle between Oracle x off-heap memory? Will sun.misc.Unsafe be removed on Java 9?

-DK

[Peter Lawrey]

Using Unsafe in Java 9 will require a special flag to be enabled. 

There will be a public API in Java 9 (in part) and Java 10 which will actually extend/replace Unsafe.

[dk.h...@gmail.com]

Hi Peter. Can you provide a source for that information? I was under the impression that they were still debating about removing off-heap memory access completely. Also if you can provide a link about this public API that will replace sun.misc.Unsafe that would be great.

Thanks,

-DK

[Peter Lawrey]

This is a good place to start https://twitter.com/paulsandoz/status/659400793229955073 It is Paul's JavaOne talk.

[bendc...@gmail.com]

Another difference (crucial to the HPC community) ... Hazelcast binds to TCP/UDP as its necessary transport, while OpenHFT empowers you to use native Linux IPC (e.g. /dev/shm) as a potential transport.

This is a delicious luxury.

LeftPingxRightPong latency tests demonstrate (emphatically) that several orders of magnitude in performance gain are realized when using /dev/shm as a transport (instead of TCP/UDP).