Just to add to the already fair reply by Martin. Take a look at how eventstore works. It tolerates a minority of servers failing, takes load similar to stock exchanges, and is OSS so you can actually read the code. https://github.com/eventstore/eventstore. You can actually find our paxos implementation in the elections service https://github.com/EventStore/EventStore/blob/master/src/EventStore.Core/Services/ElectionsService.cs .
On Sat, Sep 8, 2018 at 5:34 PM Martin Thompson <[email protected]> wrote: > Is there a mechanical sympathy question in this? If feels like someone is > curious or looking free consultancy. > > Matching engines tend to be replicated state machines. Best if you start > reading up on those. > > Martin... > > On Saturday, 8 September 2018 17:27:23 UTC+1, MechSyQ wrote: >> >> For example, on the FX or Equities exchange where HFT/real-time trading >> going on, something went terrifically wrong: not possible to save >> transaction into a file etc. What are the next actions: trading is put on >> halt developers involved? What about fail-over? Active/active is no >> application in this case? So, it is just manual or automatic fail-over from >> active to passive node? >> >> >> Thx >> > -- > You received this message because you are subscribed to the Google Groups > "mechanical-sympathy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Studying for the Turing test -- You received this message because you are subscribed to the Google Groups "mechanical-sympathy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
