[hibernate-dev] On 2nd level cache and requirements off the cache implementor

[Sanne Grinovero]

Both Ehcache and Infinispan support transactions, but Ehcache doesn't
use this capability when running as Hibernate 2nd level cache, while
Infinispan uses it more as an implementation detail to provide
internal consistency, and not to participate with the application
transaction.

So I think that the fact they both happen to also support Transactions
should be considered incidental.

I'd very interested too to hear from Galder and Alex about the
required atomic operation they build on. I could look at the code but
I'm primarily wondering of what they'd rather need conceptually, than
knowing what they are forced to do today.

Sanne

On 4 April 2014 14:27, Emmanuel Bernard <emmanuel at hibernate.org> wrote:
> This is brain storming at this stage.
>
> How much is required of a cache provider as far as semantic is
> concerned and be cluster safe? The only providers we currently offer are EhCache and
> Infinispan
> http://docs.jboss.org/hibernate/orm/4.3/manual/en-US/html_single/#performance-cache
>
> But both happen to be transactional so I wonder if that's a requirement
> and if not what are the list of atomic operations that a clustered cache
> provider would need to offer.
>
> Any hint and feedback appreciated :)
>
> Emmanuel
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev