haf
commented
12 years ago Yes, this is actually a piece of the puzzle that someone interested in learning more about F# and orchestrating services with Sagas is supposed to hack a bit at. The indexer is supposed to take a document body and make it searchable, by generating a support vector machine based on the frequently used words that are different from other documents.
The F# code for the SVM is in the docs folder and the saga support sample is on my github under 'Code4Fun.WebShotter'. Events are already coming from the domain model, that the saga is supposed to react to, sending messages to the indexer service and listening for the indexing completed event from that same service.
The aim is to have a web gui, a wpf client and a console consuming events, so when the indexing is complete, the saga would have to send the command to the document to put the document in the 'indexed' state, while transferring the index digest to the search engine to use in the GUI.
By doing this the person who tries the project out is shown how sagas/orchestration works and how a saga is a concurrent actor that receives events and sends commands ( and move things about, such as the digest ).
Anybody interested in getting their hands dirty hint hint ;)
wayne-o
It's not clear what it does or why it's in F# - could we get some explanation around this please? :)