thenativeweb/node-cqrs-saga

Issues

• Having queue in nodejs' memory makes cqrs-saga not amenable for clustering

  #47 opened 6 years ago by rakamoviz
  8

• How to make compensation if something went wrong during current saga step execution

  #49 opened 5 years ago by imissyouso
  3

• Redis SagaStore implementation bug: it creates multiple entries in redis for the same saga-id

  #46 opened 6 years ago by rakamoviz
  4

• In-memory revision guard and retry (random) timeout issue

  #45 opened 6 years ago by OrH
  4

• currentHandlingRevisions in revisionGuard never gets cleared. Possible memory leak.

  #44 opened 6 years ago by rakamoviz
  5

• i need a saga example

  #1 opened 10 years ago by izengliang
  7

• Expose development errors

  #43 opened 7 years ago by xander-mbaka
  2

• removeTimeout stops after getTimeoutCommands and getOlderSagas

  #42 opened 7 years ago by edro
  3

• Must timeouted commands really be dispatched manually?

  #37 opened 7 years ago by IRT-fbachmann
  6

• Commands added from retried sagas are not passed to onCommand handler.

  #38 opened 8 years ago by nanov
  2

• fire two commands in one event in saga

  #30 opened 9 years ago by pawarvijay
  5

• Using Saga to pass configuration data to infrastructure layers used by domains

  #36 opened 8 years ago by josh0707
  4

• MongoDB >=2.0.0 driver support

  #35 opened 8 years ago by repkins
  2

• Possible startRevisionNumber issue

  #32 opened 9 years ago by hilkeheremans
  1

• handling domain failures in saga

  #31 opened 9 years ago by pawarvijay
  3

• Loading a second aggregate during a saga?

  #16 opened 9 years ago by jdkrebs
  5

• think about optimizing with immutable objects

  #3 opened 10 years ago by adrai
  0