Re: [Quickfixj-users] Managing .seqnum files across different hosts?

[<eri...@re...>]

We’ve been doing synchronous writes to clustered Redis in testing, and while we haven't done formal benchmarking yet, it’s performed very well and is almost guaranteed to outperform any RDB. 

I am planning on moving to asynchronous writes soon, since the Lettuce API gives me a way to try to recover from failed writes.

We run fix engines in Kubernetes pods that round-robin sessions to different containers as they connect. We needed a way to share the sequence numbers, and filesystem wasn’t going to cut it.


> On Oct 31, 2018, at 19:23, Robert Nicholson <rob...@gm...> wrote:
> 
> 
> How do folks handle seqnum management in the context of secondary machines needing to know where the primary session finished when
> the secondary is activated?
> 
> I’ve seen a couple of approaches such as asynchronous writes to a shared database.
> 
> But what you don’t want is just a write to the database that’s synchronous as that would kill performance.
> 
> Has anybody successfully done this with rsync seqnum files between servers?
> 
> 
>