hemerajs/hemera

Hemera inbound/outbound duration

jeffrichie opened this issue · 5 comments

Apr 10 15:00:59 orders-service-7898c8c697-hp5jl orders-service     inbound: {
Apr 10 15:00:59 orders-service-7898c8c697-hp5jl orders-service       "id": "257d727bd48c4ff98255400105e0b9fd",
Apr 10 15:00:59 orders-service-7898c8c697-hp5jl orders-service       "duration": "567.88ms",
Apr 10 15:00:59 orders-service-7898c8c697-hp5jl orders-service       "pattern": "cmd:get,id:5,topic:forms"
Apr 10 15:00:59 orders-service-7898c8c697-hp5jl orders-service     } 

What does 'duration' mean?

Hi @jeffrichiefs duration is the time needed for the complete request / reply process.

  • Client (Send) -> NATS -> Server (Reply) -> NATS -> Client (Received)

Thanks @StarpTech - how often does Hemera poll the queue? That would be the arrows between the calls.

@jeffrichiefs which queue? The messages are routed directly through NATS. NATS act as a router.

By queue I meant NATS - Hemera looks for new messages every so often or am I thinking about this wrong?

Yes, there is no pull mechanism. NATS notify hemera about updates.