Skip to content

hewhofreeks/ObservableSaga

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

15 Commits
 
 
 
 
 
 
 
 

Repository files navigation

ObservableSaga

First run at an observale saga state using NServiceBus + SignalR

Should be easy enough to run the sample. Pull it up in a few different browsers and you can see how when you interact with one counter the rest of them change.

I'm utilizing SignalR to update the clients and NServiceBus Sagas to maintain state.

Currently CounterSaga calls the HubContext which updates the client with the updated saga data.

To dos:

-Abstract out signalr hub calls so we know what kind of hub to grab from the container for each different kind of saga. Maybe make some kind of factory that helps to determine that?

-Create front-end library to be loaded via npm to automate subscribe/listener calls

-Figure out best way to expire this sort of saga

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published