When Oak is deployed in an OSGi container, applications usually want to ship a default configuration which is different from the defaults present in Oak. E.g. an application may want to use a default cache size of 1G for the DocumentNodeStoreService instead of the default 256M. Now if a user of the application provides a custom configuration and does not specify the cache size, the value for this configuration will flip back to the Oak default of 256M.
There should be a way to configure presets for the application that are different from the Oak defaults and then allow a user to customize the configuration while still respecting the presets.