Skip to content

HA/DR #3

Open
Open

Description

@JohnGreenan

This is something a proper matching engine must have. Along with the thematically linked cancel-on-disconnect. This impacts on all aspects of the system – persisting parts of the system data to disk while not impacting performance is a balancing exercise.

Activity

  1. self-assigned this
    on Sep 6, 2023
  2. JohnGreenan commented on Sep 17, 2023

    @JohnGreenan
    CollaboratorAuthor

    There is a conceptual question to deliberate on here.
    If a production server goes down a cancel-on-disconnect will execute either implicitly or explicitly.
    So the non-production server has to commence operations with an entirely empty order book.

    All well and good, so what does need to be taken from production to non-production engine?

    Static data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions