[keycloak-dev] implement JPA model

Bill Burke bburke at redhat.com
Fri Nov 1 11:02:10 EDT 2013


Keycloak is designed right now so that we can easily swap out 
persistence engines.

I can't wait for PL 2.5.3 to be released so I can use it with Wildfly. 
I'll have a JPA model done by today so I can start bundling and testing 
Keycloak with Wildfly tomorrow.  We'll revisit Picketlink again in the 
next Keycloak release to see if it makes sense to take advantage of its 
LdAP/AD integration.  Right now though, I think we can get the biggest 
performance improvements from maintaining our own persistence engine and 
by putting targeted caching in front of it.


On 11/1/2013 10:22 AM, Anil Saldhana wrote:
> And I fall off the chair.
>
> On 11/01/2013 09:22 AM, Bill Burke wrote:
>> FYI, I'm currently implementing a JPA model.  Will switch to that
>> instead of Picketlink when its done.
>
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com


More information about the keycloak-dev mailing list