Chronicle Queue for 24/7 market

[Vero K.]

hi, we run 24/7 market and what to use chronicle to pass orders between services. 

We are a little bit confused with bit:

Typically at the end of each day you archive the queue and start the next day with a fresh empty queue.

http://chronicle.software/products/chronicle-queue/

If we are 24/7 can we close and create a new file real-time and another component will pick up it easily. how this works?

also we one of our services dies and and after that starts up again, will it be able to read all the data from chronicle and continue easily? my guess that Chronicle is just a file mapped into a memory, so I think it will persist all the messages. but the reader will know which messages it finished to read and which not? should it keep a track on the messages it processed?

thanks

[willia...@tuta.io]

Wear one wash one. Have some sort of message that signifies swapping onto another queue and then purge the other. Rinse repeat.

Definitely possible.