Managing the Current Read Position
Imagine you’re a Component subscribing to some category stream in the system. This is the sort of thing you could make a Halloween costume out of. Now imagine that you’re just booting up. The first thing you need to do is load your last committed read position.
What do you know about your committed read positions? First, you know that they’re stored in a stream whose name is in subscriberStreamName, so the position will be in a message. How’s that for dogfooding the Message Store? Second, you know you only write to this stream every positionUpdateInterval messages, so when you’re first getting started, you won’t actually find any written position in the store. Also, you’re just appending to this stream the ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access