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.

Sign up for GitHub

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

Jump to bottom

Separate amqp connection for ingress and egress #46

Closed
rhinof opened this issue Apr 25, 2019 · 1 comment
Closed

Separate amqp connection for ingress and egress #46

rhinof opened this issue Apr 25, 2019 · 1 comment
Labels
good first issue Good for newcomers tech debt technical debt that should be payed off
Projects
v1.1

Comments

@rhinof
Copy link
Contributor

rhinof commented Apr 25, 2019

In order for the producers and consumers workloads will not interfere with one another each should use a dedicated amqp connection.
@rhinof rhinof added tech debt technical debt that should be payed off good first issue Good for newcomers labels Apr 25, 2019
@ghost ghost self-assigned this Jul 1, 2019
@ghost ghost mentioned this issue Jul 3, 2019
Merged
@ghost
Copy link

ghost commented Jul 3, 2019

PR: #97

@rhinof rhinof added this to In progress in v1.1 Jul 3, 2019
@rhinof rhinof moved this from In progress to Done in v1.1 Jul 4, 2019
@rhinof rhinof closed this as completed Jul 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers tech debt technical debt that should be payed off
Projects
No open projects
v1.1
  
Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rhinof