issues
search
thenativeweb
/
node-cqrs-saga
Node-cqrs-saga is a node.js module that helps to implement the sagas in cqrs. It can be very useful as domain component if you work with (d)ddd, cqrs, eventdenormalizer, host, etc.
http://cqrs.js.org/pages/saga.html
MIT License
61
stars
16
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Bump mongodb from 2.1.21 to 3.6.1
#52
dependabot[bot]
opened
4 years ago
0
Bump lodash from 4.17.15 to 4.17.19
#51
dependabot[bot]
closed
4 years ago
0
How to make compensation if something went wrong during current saga step execution
#49
imissyouso
opened
4 years ago
3
Bump lodash from 4.17.11 to 4.17.15
#48
dependabot[bot]
closed
4 years ago
0
Having queue in nodejs' memory makes cqrs-saga not amenable for clustering
#47
rakamoviz
opened
5 years ago
8
Redis SagaStore implementation bug: it creates multiple entries in redis for the same saga-id
#46
rakamoviz
opened
5 years ago
4
In-memory revision guard and retry (random) timeout issue
#45
OrH
closed
5 years ago
4
currentHandlingRevisions in revisionGuard never gets cleared. Possible memory leak.
#44
rakamoviz
opened
5 years ago
5
Expose development errors
#43
xander-mbaka
closed
6 years ago
2
removeTimeout stops after getTimeoutCommands and getOlderSagas
#42
edro
closed
6 years ago
3
Saga handlers may be synchronous or return Promises instead of using callbacks
#41
IRT-fbachmann
opened
7 years ago
6
Support default exports.
#40
IRT-fbachmann
closed
7 years ago
0
Fix saga callback on retry
#39
nanov
closed
7 years ago
0
Commands added from retried sagas are not passed to onCommand handler.
#38
nanov
closed
7 years ago
2
Must timeouted commands really be dispatched manually?
#37
IRT-fbachmann
closed
6 years ago
6
Using Saga to pass configuration data to infrastructure layers used by domains
#36
josh0707
closed
7 years ago
4
MongoDB >=2.0.0 driver support
#35
repkins
closed
7 years ago
2
Update uuid to version 3.0.0
#34
marcbachmann
closed
7 years ago
0
Fix events getting lost at high concurrency
#33
hilkeheremans
closed
8 years ago
5
Possible startRevisionNumber issue
#32
hilkeheremans
closed
8 years ago
1
handling domain failures in saga
#31
pawarvijay
closed
8 years ago
3
fire two commands in one event in saga
#30
pawarvijay
closed
8 years ago
5
Fixed issue with `defineShouldHandle()`.
#29
jwoudenberg
closed
8 years ago
0
Loading a second aggregate during a saga?
#16
jdkrebs
closed
8 years ago
5
think about optimizing with immutable objects
#3
adrai
closed
9 years ago
0
Add azureTable support
#2
rvin100
closed
9 years ago
0
i need a saga example
#1
izengliang
opened
10 years ago
7