Does hazelcast support Synchronized caching ?

[snehb...@gmail.com]

Does hazelcast support synchronized caching and can i use it with spring as per the spring documentation?
If it does, is there a way to timeout the thread that is being executed (based on certain threshold) ? What would be the behavior for the waiting threads in that case?
I am new to hazelcast and am trying to understand how can i add this feature if its currently not supported.
Greatly appreciate any pointers.

Thanks,
Sneh

[Lucas Beeler]

Hi Sneh,

Hazelcast's EntryProcessor abstraction implicitly locks entries while lengthy computations are being performed on them. Indeed, the standard Java caching specification, JCache, standardized as JSR-107 (full text available here) borrows the name "EntryProcessor" and this behavior from the Hazelcast API. Javadoc for the Hazelcast EntryProcessor is available here.

Now, I know you also asked about Spring. The short answer is yes: Hazelcast's Spring bindings have supported synchronized caching since Hazelcast 3.7 in this git commit. This implementation uses the Hazelcast Map.lock( ) and Map.unlock( ) methods, which is the same mechanism that the EntryProcessor uses.

Take care,

Lucas

--
You received this message because you are subscribed to the Google Groups "Hazelcast" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hazelcast+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hazelcast/7703169d-3ed4-4a2d-bc70-fa120d23545eo%40googlegroups.com.

--

Lucas BEELER Principal Solutions Architect       hazelcast®     2 W 5th Ave, Ste 300 | San Mateo, CA 94402 | USA +1 (650) 521-5453 | hazelcast.com

This message contains confidential information and is intended only for the individuals named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required, please request a hard-copy version. -Hazelcast