A component family can provide a file/record compression definition.

With TCOMP-253, the component framework can add business objects with common logic.

Component families can provide a FileCompressionDefinition that represent which codec should be used to compress a file or message and any configuration.

Components that support compression should support any compression definition stored in the component framework. As an example, a text output component should be able to compress the text file in any of the FileCompressionDefinition instances available.

Some file formats do not support arbitrary compression formats – for example, the internal block compression for Avro is either "null" (none) "deflate" (gzip) or "snappy".