microprofile-config VS gestalt

There are a lot of great config libraries, you should also take a look at such as smallrye-config. I am trying to make my library compatible with microprofile-config but there are some fundamental differences.

You might have a look at MicroProfile Config as well.

Now you might be tempted to say well we just need a System.getProperties replacement. A SLF4J of properties config. Perhaps one that uses the ServiceLoader. And indeed microprofile config somewhat solves that problem. The problem is of course is backward compatibility (replacing all the old libraries uses of system properties of which you might not be able to) and of course that config facade adds a dependency.

Quarkus is internally using the SmallRye implementation of Eclipse MicroProfile Config (MP-Config). MP-Config allows to add so called Configuration Sources, that allow to supply config objects in a programmable way from e.g. a file in a strange format or perhaps even from a central repository. This brief post describes how to create a ConfigSource for Quarkus that knows about existing properties

Feel free to take a look at Gestalt for use in your library, i welcome any feedback and try and keep it up to date as possible. I have used it in a few projects at work (in production), but we have mostly moved over to Spring, so haven't been using it as much. Although i still enjoy working on it and adding new and interesting features.

I have a library Gestalt that de-serializes configuration properties into objects. It checks for a setter and uses that first, but if not found it leverages setAccessable on the field to set the value from the configuration.

This, i have a project https://github.com/gestalt-config/gestalt and the java API has 12 methods, i wanted to add another optional parameter but i didn't want 24 methods.

Thanks for including my library, Gestalt Config . it was a nice surprise to see it on the list!