(does one pronounce MLFE as "milfy"?)
(does one pronounce MLFE as "milfy"?)
The only thing needed is support for dynamic loading and unloading of modules.
The biggest problem, which dynamic systems also suffer from, is how to smoothly perform the updates with inflight requests.
Unload all the modules and reload them again.
In Cedar, or ETHZ Oberon for that matter, all executables are dynamically loaded and can be either used by other modules or exposed to the user as commands.
Loading a new version means unloading the module and its dependencies.
When it gets re-loaded it has a the new interface available.
Of course, there is the issue to solve any possible compilation errors before the module can be loaded again.
A similar approach can be done in Java and .NET via classloaders and app domains respectively.