Open
Description
It should be possible to add dynamic periodic events during runtime. This could be useful if periodicity is driven by the business process and it's different on a tenant basis.
Concept Idea:
- add a new db table for
runtimeEventConfig
- periodic events added during runtime are stored in this table
- would this also make sense for ad-hoc events? Not sure yet
- every application instance would be informed via redis is a new event config is added
- without redis db polling
- every app needs to fetch this information during startup
- with redis this could also be done once and than shared. Benefit is less db connections are needed. Not sure yet
- The event config class needs to be tenant aware in order to store tenant specific configuration
- with redis this could also be done once and than shared. Benefit is less db connections are needed. Not sure yet
- Question is: Would be allow multiple periodicity for the same event?
- This could be archived by adding a suffix to the type. This would need to be reflected in the db table for
runtimeEventConfig
as well.
- This could be archived by adding a suffix to the type. This would need to be reflected in the db table for
- deletion of a
runtimeEventConfig
would need to be propagated to all instances and entry needs to be removed from event table and event config (runtime)
I easier solution could be (needs evalutation):
- add new logic after a periodic event that calcs the next event
- would require to extend the event table to store the periodicity