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

Decouple receiving processes from the DB and MQ #84

Open
dajtxx opened this issue Jun 21, 2024 · 0 comments
Open

Decouple receiving processes from the DB and MQ #84

dajtxx opened this issue Jun 21, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@dajtxx
Copy link
Collaborator

dajtxx commented Jun 21, 2024

Restarting the entire system is not a problem in our use-cases, but it is frustrating that receivers need to be stopped when almost all code updates do not affect them.

There is also an argument that decoupling the receivers from the rest of the system would make it easier to deploy in security-constrained environments. For example, if the receivers could run in a DMZ and the rest of the system could retrieve messages by calling out to the DMZ it would provide a more secure deployment.

This would perhaps require a 2nd MQ - one running for the receivers and one running for the rest of the system. Alternatively, FTP or scp could be used to get messages.

@dajtxx dajtxx added the enhancement New feature or request label Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant