[keycloak-dev] openshift cartridge vs. saas

[Stian Thorgersen]

Sounds like a good idea to me. 

It's simple. Works around the potentially huge issue of scaling. There's already a billing model for OpenShift. With premium cartridges available as well, so when there's a supported Keycloak product available that's a mechanism to get paid support.

Also, I think some people will be more happy about dedicated instances for several reasons (performance, isolation, ownership, etc.).

----- Original Message -----
> From: "Bill Burke" <bburke at redhat.com>
> To: keycloak-dev at lists.jboss.org
> Sent: Tuesday, 6 August, 2013 5:26:37 PM
> Subject: [keycloak-dev] openshift cartridge vs. saas
> 
> Having a dedicated openshift cartridge for keycloak would be very cool.
>   The question is, maybe we should do this instead of a Intranet SaaS?
> We could have a demo realm and demo apps, with a read-only admin UI.
> Given the rumored clustering problems with openshift maybe this would be
> a better approach?
> 
> What would be cool about this, is that the user could assign a domain
> name to their admin server.  Maybe the Keycloak SaaS could turn into
> solely a registration page that triggers an openshift provisioning script.
> --
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>