Currently, 2.x branch has a ServerEnvironment which assumes that several Bounded Contexts always share the same settings (i.e. StorageFactory, TransportFactory etc) if they are deployed in scope of a single JVM. Such an arrangement allows to keep the code relatively simple and give a clear advice on the deployment strategy.
In scope of this task, we need to discuss other options. Put it simpler: do we want to make the code more complex, but support the rare case of running contexts in a single JVM with different env. settings?
armiol
commented
3 years ago
Currently, 2.x branch has a
ServerEnvironmentwhich assumes that several Bounded Contexts always share the same settings (i.e.StorageFactory,TransportFactoryetc) if they are deployed in scope of a single JVM. Such an arrangement allows to keep the code relatively simple and give a clear advice on the deployment strategy.In scope of this task, we need to discuss other options. Put it simpler: do we want to make the code more complex, but support the rare case of running contexts in a single JVM with different env. settings?