API Event/Message Queue? #144
Description
There area few areas where having an event/message queue would be useful, for example:
- DAMNIT related events
- New instance set up?
- Context file updated
- Processing (run) status
- Internal caching/revalidation
- Revalidate cached info from MyMdC when it expires instead of only on user queries
- Same for user proposal lists
- SLURM stuff?
- Misc. info (e.g. run migrated)?
Currently where required (gql subscriptions) this is handled with polling per instance, since IMO we have a number of areas where we need to act on external events it would make sense to move this logic to an internal queue.