Just working through the example, when I’m reading an item from the queue (i.e. streams/newstream/0) the item stays in the queue - using DELETE at the item-id level does not appear to work, so a couple questions:
How do you remove item “0” from streams/newstream - or am I just doing it wrong?
The “subscriber” example is just polling - does Event Source support a push model for notifying workers as the queue has new items added or is polling the only supported approach out of the box?
What is the recommended pattern for data consistency - i.e. how do I ensure that if a client consumes an item from the queue but crashes, the work does not become lost?
Looks really straight forward and nice, looking forward to working with Event Store in the future :).