Re: [jakarta.ee-community] Discussion on moving the JSR107 specification (JCache) to JakartaEE
I think there is important context to be added here. Including
JCache into Java/Jakarta EE is a discussion that has been active
for a very long time. This is so much so, that it wound up as a
key question in the Java EE 8 survey:
A consistently large number of Java/Jakarta EE developers have
expressed interest in this (almost 70% of developers in the survey
- see attached). I think we all know the reasons why it didn't
happen in Java EE 8 despite these results.
The primary drivers to include JCache I think remain relevant
* A large number of enterprise applications use the technology to
boost performance in mission critical applications.
* The application state cache (HTTP sessions, etc) can be
offloaded to JCache implementations in the way runtimes like Open
Liberty do today:
* The JPA second level cache can be offloaded to JCache
* Yes, it's all relevant for microservices and the cloud to
reduce network latency in a highly distributed system. This is why
we have things Azure Redis Cache:
In addition I think there are the following drivers:
* Bette JCache integration with CDI.
* Bette JCache integration with JTA/JCA.
* Evolving JCache to incorporate reactive concepts (though I
would think about standardizing this after seeing how Loom plays
Other than the IP and code transfer, I think this is an easy win
for Jakarta EE that does not really involve heavy investment. Most
of the work I think is basically already done here and there such
as by the Payara folks:
and the Data Grid JSR.
Jakarta EE Ambassador, Author, Blogger, Speaker
Please note views expressed here are my own as an individual
community member and do not reflect the views of my employer.
On 1/19/2022 11:05 AM, 泠 恒谦 wrote:
Hi friends of the community.
JSR107 (JCache) About. JCache is the Java caching
API. It was defined by JSR107. It defines a standard
Java Caching API for use by developers and a
standard SPI ("Service Provider Interface") for use
The mandatory requirement is of course that it must
first migrate to the new namespace. Whether they
want to do that or not depends entirely on the
Maintenance Leads @gregrluck and Oracle. After its
MR2 I guess May 2019 there has been absolutely no
activity, so between JCrete (also 2019) when Greg
and I briefly spoke about it and now there was no
activity not even fixing any bugs or merging PRs.
some friends will pay attention to this topic, maybe the
migration problem is related to Oracle’s legal approval.
Finally, I would like to
thank Tanja Obradovic for the invitation.
jakarta.ee-community mailing list
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-community
Description: PNG image