Working with a Managed Flux Runtime
A Deployment unit consists of user code and configuration that is to be "deployed" to the Flux runtime running in Managed Mode so that user given tasks can be executed inside Flux JVMs. Each Deployment Unit is loaded using a separate class loader.
The same user code would exist in user application as well. A workflow is said to be "invoked" when a @Workflow annotated method is invoked within the Client application. The Flux Client residing in user application intercepts all workflow invocations and transforms them into Flux's State Machine representations and submits them to the Flux Runtime for execution.
As shown, the Deployment unit is expected to contain User code, Dependencies (jars) and configuration so that it can be loaded within the Flux core runtime.
Flux reads all available deployment units on bootup. Also deployment units are loaded dynamically by placing the files on disk and making a rest call, refer Deployment Unit section for more details.