MicroservicesTalkIdeas

Updater - Dependency Mgmt @ Runtime - Possibility to roll back updates @ runtime?

Idea example:
- Let's say, we want to update the application. Instead of the single event it was before, it's much more dynamic
-> Download a new version of the library part (e.g. StoreEventHandling.dll v1.1 from 1.0)
-> Download all depedent updates if there are any (e.g. StoreEventHandling.dll 1.1 requires core 1.2)
-> Now this won't be live on next launch, but can be controlled via some meta data
-> This enables us to test an update, but when something important fails, we can go back to the previous version anytime
-> This is either controlled by a central update server or by the client, based on some metrics (increased error count something something)

---> What would be required is an ultra stable core, which cannot fail. If something goes wrong in one module, ideally, the application does not event
   > need to be restarted, but the core would roll back to previous library versions (like microservices but for libraries)
   
Base could be NInject or similiar, check how flexible that stuff is