Moleculer: NATS Streaming transporter

[icebob]

https://github.com/nats-io/node-nats-streaming

[icebob]

https://github.com/ice-services/moleculer/tree/nats-streaming

[icebob]

Dropped

[icebob]

https://dev.to/byronruth/use-cases-for-persistent-logs-with-nats-streaming

[TomKaltz]

Why dropped?

[icebob]

When I tried to implement it, I couldn't figure out how to set which topic will be stored, so the server stores all messages including internal messages (DISCOVER, HEARTBEAT...etc) But for event sourcing, we need to store the EVENT messages only.

Otherwise, the branch exists, so somebody can continue it.

[TomKaltz]

Might need to use both regular NATS and NATS Streaming separately for
different use-cases. Would this be a good design to support both via
option in Broker?

On Thu, Jan 18, 2018 at 4:05 AM, Icebob [e-mail] wrote:

When I tried to implement it, I couldn't figure out how to set which topic
will be stored, so the server stores all messages including internal
messages (DISCOVER, HEARTBEAT...etc) But for event sourcing, we need to
store the EVENT messages only.

Otherwise, the branch exists, so somebody can continue it.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ice-services/moleculer/issues/104#issuecomment-358582135,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC0_IfFRUbG3YeI38iQraU9Fq_SIDP1Zks5tLwk-gaJpZM4PhMlQ
.

[zllovesuki]

It's possible to have an eventSourcing option alongside with transporter. In that case, eventSourcing only accepts NATS Streaming or Kafka (and maybe optionally rejects those on transporter). I will take a look at that branch once I'm less busy...