ContentTypeFactoryImpl Getting Config values cause unneeded load

[wezell]

In our containerized world, we do not need to support on the fly configuration changes or configuration reloading any longer. Instead of relying on apache classes, file watchers, and other blocking patterns, we should just read in the configuration at startup as an immutable map and use it as needed.

For example, in the ContentTypeFactoryImpl we call this whenever the class is inited (which happens a lot as it is not a singleton).

  final boolean LOAD_FROM_CACHE=Config.getBooleanProperty("LOAD_CONTENTTYPE_DETAILS_FROM_CACHE", true);

It turns out, our Config class is not really that performant. In this case, I see this a performance hotspot as java builds the exception's stack trace.

There are multiple places in our code where you can see performance issues with our use of the class.
org.apache.commons.configuration.AbstractConfiguration

If we ever need a mechanism to update config on the fly in the future, we can write something then to do so by replacing the map, etc.

[freddyucv]

Hey team! Please add your planning poker estimate with ZenHub @dsilvam @victoralfaro-dotcms

[jdotcms]

I was working on this PR: https://github.com/dotCMS/core/pull/19976/files
My idea was to create a service that provide the config on memory using an API instead of the Config
You can take a look

[freddyucv]

I was working on this PR: https://github.com/dotCMS/core/pull/19976/files My idea was to create a service that provide the config on memory using an API instead of the Config You can take a look

@jdotcms @wezell it still has work to do but I think it is going to solve the Bug, right?

[wezell]

PR #22143

[fabrizzio-dotCMS]

new PR #22209