|
|
|
|
|
|
by efecan0
344 days ago
|
|
|
It looks similar on the surface, but scope and goals are different: * BinaryRPC = direct request/response calls with optional QoS (per session).
– No exchanges/queues, no routing keys.
– One logical stream, messages mapped to handlers. * RabbitMQ / AMQP = full message-broker with persistent queues, fan-out,
topic routing, etc. So you could say BinaryRPC covers the transport/QoS part of AMQP,
but stays lightweight and broker-less.
If an app later needs full queueing we can still bridge to AMQP, but the core
idea here is “RPC first, minimal deps”. |
|
|