[keycloak-dev] Redis cluster instead of Infinispan

Adrien DESBIAUX adesbiaux at vente-privee.com
Mon May 7 15:59:10 EDT 2018


Hi Marek,


Thanks for your feedback on this.


In regards to maintenance I think Infinispan is as hard as Redis.


What I find difficult is related to the little amount of content the one can find on the web when facing an Infinispan related issue. There is not that much Stack Overflow threads about Infinispan and "case studies".


I do understand that from a strategy point of view it may not be in the interest of RedHat to support another solution outside of the "JBoss set of tools".


However from a developer/devOps point of view it would be, I believe, way more enjoyable to setup a Redis rather than an Infinispan, especially when it comes to have some clues about how to tweak and scale the solution. It would also potentially increase the range of adoption.


Cheers!

________________________________
From: Marek Posolda <mposolda at redhat.com>
Sent: Monday, May 7, 2018 6:34:56 PM
To: Adrien DESBIAUX; keycloak-dev at lists.jboss.org
Subject: Re: [keycloak-dev] Redis cluster instead of Infinispan

Hi,

in theory you can do it, but you will need to override some providers
(user session provider, caching providers) to use redis instead of
infinispan. It may be fair amount of work.

I don't think we have a plan to replace infinispan with the Redis and
support it OOTB. One thing is to develop the Redis support, but another
is maintenance, which is even more difficult. Especially considering
that we need to care about backwards compatibility and support for
rolling-upgrades in the future...

What kinds of issues you had in infinispan? Are there some concrete
issues you saw?

Marek


Dne 4.5.2018 v 10:11 Adrien DESBIAUX napsal(a):
> Hello all!
>
>
> What would be the effort required in order to add a Redis connector in place of the classic Infinispan?
>
> Wildfly would have to be updated as well as Keycloak?
>
>
>
> Indeed we found out Infinispan extremely difficult to setup and the documentation very complex to digest.
>
>
> Also being able to plug a Redis cluster would speed up the Keycloak adoption.
>
>
> What is your opinion on this topic?
>
>
> Thank you in advance for sharing your thoughts.
>
>
> Cheers,
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.jboss.org_mailman_listinfo_keycloak-2Ddev&d=DwICBA&c=8G9fL-FODW3I-fESjFvsaw&r=BhQIS0sALperhBRJRNzxM3Ax9g4k8rNIuzNmM35TMgE&m=BawETuB5tx_R5j7UxcgqAWEzI25TLAYCkmsqqOJHCco&s=hSU7ExTWtYmZFQT9e4EDpZUM3Q3-f5Rn9FraW_pvSLw&e=




More information about the keycloak-dev mailing list