Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Concurrent message processing #20

Open
dartvandru opened this issue Sep 29, 2016 · 0 comments
Open

Concurrent message processing #20

dartvandru opened this issue Sep 29, 2016 · 0 comments
Assignees

Comments

@dartvandru
Copy link
Collaborator

Events with the same eventType and swimlane MUST BE processed sequentially. All other events can and should be processed concurrently.

In the Java code, SwimlaneBasedDispatcher.java maintains a separate queue of events for each swimlane (BUG it should be eventType and swimlane). A thread based mechanism pulls events from the queue and processes them one at a time. NodeJS doesn’t have threads but I’d imagine a callback-based messaging would be good:

  • When the processing of one message completes, get the next message from the queue if there is one
  • Each queue keeps track of whether processing is happening so that after adding an event to the queue:
    • If not processing, start processing
    • If processing, do nothing - event will be processed eventually
@dartvandru dartvandru self-assigned this Sep 30, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant