[keycloak-dev] wildfly pkg manager changes everything

[Stian Thorgersen]

I don't have the full picture yet on how this will all work, but it sounds
really promising.

There are at least 3 categories of users for Keycloak:

* Black box users - built-in features and config options are sufficient
* Middle ground - customized themes and a few custom providers, but still
happy with a default setup with regards to subsystems (and limited use of
JEE features)
* Integration - more heavily customized and have a need to add additional
subsystems on top of what we bring

I would believe most users land in the first two and would be happy with a
single distro download rather than having to install a package manager to
then install. For the latter the approach to combine your own would be
great.

Same applies to Docker and OpenShift distributions. We still need a ready
out of the box option as well as the "install your own" option.

On 4 April 2018 at 23:53, Bill Burke <bburke at redhat.com> wrote:

> Had a long talk with Jason Greene today and one of the things that
> came up was the Wildfly Package Manager that is being developed.
>
> You'll be able to pull in the exact subsystems, modules, you want,
> even  as fine grain as saying "I don't want EJB remoting".  You'll be
> able to update,  at will,  all or parts of the install.  This
> completely changes patch management for all of us.  You'll be able to
> easily create and extend distros and service packs.  Service packs
> that depend on service packs.  A lot of interesting combinations. They
> are also looking into various ways to organize an image hierarchy so
> even how we build images for keycloak may change.  It is all maven
> artifact based, which means that a service pack definitions,
> distributions, images, installations are measured in kilobytes rather
> than hundreds of megabytes as these definitions point into maven
> repos.  Its not limited to Java either and will be able to really
> package manage anything...cross platform as its written in Java.
>
> This brings a smile to my face as we can ditch this whole monolithic
> distribution approach we currently have with bare metal and
> docker/openshift.  Keycloak, IMO, has always been more of an
> integration platform than a black box appliance and this will be a big
> boon to developers that want to optimize their distribution, memory
> consumption, image size, etc.
> --
> Bill Burke
> Red Hat
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>