I suppose you have a database on the query side, and you want to replay events so that the database of your query side gets updated. The tracking processor will do this job, using a token (stored in the tokenStore) , in which token the processor will store its “progress”. All this happens within a context of one service(in your case the query side). What you do in command side, and how you populate your event store etc, is irrelevant to the query side.
The query side service has to have configuration for connection to the event Store, for the tracking processor, and for the token Store.
So in short, you need to have in the query side service, the same configuration you have for the command side service, regarding the event store , plus the configuration for the tokenStore and the tracking processor.
Στις Τετ, 12 Σεπ 2018 - 21:44 ο χρήστης Gustavo Monti <email@example.com> έγραψε: