<div dir="ltr"><div><div>That's good to hear.<br><br></div>By 'JavaEE style clustering' I meant a model where state is held in-memory by application servers which talk directly to each other. In comparison to a <a href="http://12factor.net">12factor.net</a> style model where state is held outside the application server - this being a model which simplifies deployment models (albeit by adding a constraint) which is popular both with people rolling their own infrastructure, and using PaaS solutions - Heroku, CloudFoundry etc.<br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 14, 2015 at 2:12 PM, Bill Burke <span dir="ltr"><<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The abstraction will still againt and it will still be possible to plug in your own session implementation. But we don't think using JPA or Mongo is a good solution for manganging UserSessionModel. That's the biggest reason we are deprecating it.<br>
<br>
FYI, not sure what you mean by "JavaEE style clustering". Infinispan is just a distributed cache/data grid and nothing to do with Java EE. I don't see how Infinispan is any different than Redis.<span class=""><br>
<br>
On 8/14/2015 3:42 AM, David Illsley wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
I'd really like to be able to run Keycloak without relying on JavaEE<br>
style clustering, and instead rely on modern 12-factor approaches. I was<br>
planning to do that by implementing a bunch of interfaces to use redis<br>
rather than JPA/Mongo/Infinispan, so I'm keen that you don't tie things<br>
too tightly to infinispan (not that I think you would. infinispan and<br>
redis effectively provide simple key/value stores).<br>
<br>
On Tue, Aug 4, 2015 at 5:57 PM, Bill Burke <<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a><br></span><span class="">
<mailto:<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>>> wrote:<br>
<br>
Hi all,<br>
<br>
Keycloak team would like to deprecate and remove the JPA and Mongo<br>
stores for UserSessions and just provide an Infinispan one. It is a<br>
pain to maintain these, and in our opinion, users really shouldn't be<br>
using JPA or Mongo to store User Sessions. Infinispan has a wide<br>
variety of configuration options for internal, external, and cloud<br>
networks.<br>
--<br>
Bill Burke<br>
JBoss, a division of Red Hat<br>
<a href="http://bill.burkecentral.com" rel="noreferrer" target="_blank">http://bill.burkecentral.com</a><br>
_______________________________________________<br>
keycloak-user mailing list<br></span>
<a href="mailto:keycloak-user@lists.jboss.org" target="_blank">keycloak-user@lists.jboss.org</a> <mailto:<a href="mailto:keycloak-user@lists.jboss.org" target="_blank">keycloak-user@lists.jboss.org</a>><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-user" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-user</a><br>
<br>
<br>
</blockquote><div class="HOEnZb"><div class="h5">
<br>
-- <br>
Bill Burke<br>
JBoss, a division of Red Hat<br>
<a href="http://bill.burkecentral.com" rel="noreferrer" target="_blank">http://bill.burkecentral.com</a><br>
</div></div></blockquote></div><br></div>