Context
Currently our image creations is 'one size fits all' paradigm. That causes a large image size even for basic cases configurations i.e. InMemory.
Idea here is to optimize our image creation. Few area's on how we can do is,
Optimize based on cdd - OOB based on the cdd values for OM, Store, Metrics, etc.
Exclude some obvious libs which will not come into place at runtime like cep-docker, etc.
Exclude specific modules/jars - Allow end user based on their implementation needs to exclude certain libraries/modules, such as if using HTTP channel, they can exclude other channel jars or say remove JSON libraries if using only XML or remove predictive analytics libs if its not being used.
Clean up some libs/config/bin/etc folder contents off JRE.
Alternatives
None so far.
Has the feature been requested before?
Yes
If the feature request is approved, would you be willing to submit a PR?
Yes
Context Currently our image creations is 'one size fits all' paradigm. That causes a large image size even for basic cases configurations i.e. InMemory.
Idea here is to optimize our image creation. Few area's on how we can do is,
Alternatives None so far.
Has the feature been requested before? Yes
If the feature request is approved, would you be willing to submit a PR? Yes