externalized-properties VS microprofile-config

https://github.com/joel-jeremy/externalized-properties - A proxy based configuration library

P.S. I am the author of the Externalized Properties library. The primary reason I created the benchmark is to test how this library fares against the other existing configuration solutions. Just thought of sharing the results here in case others may find it useful. :)

I just released an alpha version via Maven Central. Feedback is very much appreciated! Installation instructions can be found in README: https://github.com/joeljeremy7/externalized-properties

I just released an alpha version via Maven Central. Feedback is very much appreciated! Installation instructions can be found in README: https://github.com/joeljeremy7/externalized-properties

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