Request/reply?
See original GitHub issueI’m attempting to implement this library using request/reply. I seem to be able to reply on the subscription end fine, but I’m not seeing a way to receive that reply on the publisher side. I tried using plain node-nats
on the publisher side but that doesn’t seem to ever fire the response callback.
Is there a way to do this with this library, or will there be a way to do it in the future? Or am I missing some fundamental concept? I understand this library is a work in progress, I don’t intend to sound pushy.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Request-Reply - Enterprise Integration Patterns
When an application sends a message, how can it get a response from the receiver? Send a pair of Request-Reply messages, each on...
Read more >Request–response - Wikipedia
In computer science, request–response or request–reply is one of the basic methods computers use to communicate with each other in a network, in...
Read more >Request Reply - Apache Camel
Send a pair of Request-Reply messages, each on its own channel. Camel supports Request Reply by the Exchange Pattern on a Message which...
Read more >SanderMertens/dds-requestreply: A request-reply ... - GitHub
dds-requestreply. A request-reply example using vanilla OMG DDS. Description. A server and a client process exchanging one request and a reply.
Read more >Request/Reply - Solace API Tutorials
Request/Reply. 10 Minute Read. This tutorial outlines both roles in the request-response message exchange pattern. It will show you how to act as ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That’s a good idea, I’ll definitely look into that. Thanks!
One pattern you could use it to provide a database proxy, this worker could be part of a queue group, and only this type of worker connects to the database and consumes database events. Then you can scale your database connections as needed, but they are not tied to the other workers you have.