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

backend to backend communication #48

Closed
k1ng440 opened this issue May 8, 2018 · 3 comments
Closed

backend to backend communication #48

k1ng440 opened this issue May 8, 2018 · 3 comments
Labels
enhancement help wanted

Comments

@k1ng440
Copy link

k1ng440 commented May 8, 2018

Please add

  • tcp
  • rabbitmq
  • nats
@cainlevy
Copy link
Member

This has potential. RabbitMQ and NATS best practices are outside of my expertise, though, so this is unlikely to proceed without help.

To clarify:

  • TCP is the current implementation, yes?
  • This would affect both inbound (internal endpoints) and outbound (webhook) communication?

@k1ng440
Copy link
Author

k1ng440 commented Jun 12, 2018 •
edited
Loading

I think GRPC would be enough for backend communication.

  • TCP is the current implementation, yes?
    Yes
  • This would affect both inbound (internal endpoints) and outbound (webhook) communication?
    Yes

@mohammed90 mohammed90 mentioned this issue Nov 2, 2018
Closed
@cainlevy
Copy link
Member

cainlevy commented Nov 3, 2018

Closing in favor of #78

@cainlevy cainlevy closed this as completed Nov 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cainlevy @k1ng440