Hi Les, Le 12/01/2014 03:14, Les Hazlewood a écrit :
Hazelcast can easily run in the same process-space (in-memory) as your application, and it's a java .jar file - no 'installation' necessary. Deployed this way (as a simple .jar file included in your app), Hazelcast is effectively the same as a Guava cache: they're both single-JVM/in-memory and both lightweight. To put it another way, Hazelcast and Guava are (effectively) equal choices in this deployment mode.
Nice. If Hazelcast allows such an embedded mode, it's a good solution to go and Guava implementation should not be provided :-)
But here is why Hazelcast can be better than Guava, especially as a default cache solution: the instant you decide you need to move beyond simple in-memory/in-process caching, you just have to 'turn on' Hazelcast's clustering.
I understand your point of view. Actually, I'm just usually more skeptical than necessary when one talk me about a solution that seems to fit the needs "whatever they are". But I must admit I didn't gave any chance to such solutions about caching: i'll try to drop an eye on Hazelcast soon.
Thank you for opinion. Regards. -- Brendan Le Ny, Code Lutin [email protected] (+33) 02 40 50 29 28
