Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create messaging concept #397

Open
mmacata opened this issue Dec 13, 2022 · 0 comments
Open

Create messaging concept #397

mmacata opened this issue Dec 13, 2022 · 0 comments
Labels
actinia as a service enhancement New feature or request plugin does not concern actinia-core but one of the plugins

Comments

@mmacata
Copy link
Member

mmacata commented Dec 13, 2022

As more an more plugins are developed, it is not feasable to differ between them only by using another endpoint. This current approach makes it hard to chain different plugins and is not very flexible.
The task here should be to come up with a concept which allows different plugins to be chained. Message queue / broker could be a cool approach with redis already needed by actinia and job queue already possible via redis.
The concept should be flexible, so that the "chain" works, even though not all plugins are always installed.

@mmacata mmacata added enhancement New feature or request plugin does not concern actinia-core but one of the plugins labels Dec 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
actinia as a service enhancement New feature or request plugin does not concern actinia-core but one of the plugins
Projects
None yet
Development

No branches or pull requests

2 participants