I do not believe there is an issue to be concerned about regarding size of the serialized object - that is a premature optimization decision.  In terms of finding a suitable object that only contains name, type (properties?), definition - I didn't want to introduce a new class for that purpose in this PR.  In fact, I think ModuleDefinition is actually an appropriate name for the current purpose given the current use of StreamDefinition but would remove the 'runtime' resource/classpath fields.  A new class, like RuntimeModuleDefinition, would then encapsulate that additional information and also would mean that the current ModuleRegistry would be something like RuntimeModuleService or something vs. the current mixing of ModuleDefintionRepository and ModuleRegistry usage.  

Would be good to talk about it as part of a parking log discussion at the end of the next stand up call.