5 things I wish I knew before writing an financial exchange

    System Analysis and Software Engineering,  Reactive programming

    “Tell me, and I will forget. Show me, and I may remember. Involve me, and I will understand.”

    When I and my cat set off to developing a financial exchange engine, this very quote of Confucius was ringing in my head. We were a dream team: motivated, solid, result-oriented. Our condition could be best described as interest and readiness to take on challenges on our way to MVP. All those challenges and discoveries, met during development, have adjusted the whole process and were well worth the time spent. Today I’d like to share some of them with you — and tell about the results of this experiment as well.

    For the impatient, here is the link to the self-hosted demo. The rest, please, welcome to read further.

    Vonmo Trade Experiment. Part 2: Orders. Types and processing features

    System Analysis and Software Engineering,  Reactive programming

    To figure out how exchanges work, we need to look into exchange orders and the way broker processes them. This article deals with order types, the way they are executed at an exchange, and limitations imposed by trading system.
    If you are curious to know what all those DAY, GTC, FOK, IOC, GTD, GAT, MOO, MOC, LOO, LOC, MIT, OCO, OSO, PEG mean, you are welcome.

    Vonmo Trade Experiment. Part 1: Exchanges and modern technologies

    System Analysis and Software Engineering,  Reactive programming

    This series of articles describes an attempt to create a reactive system performed by one person, with a minimum budget and in the shortest time possible.

    The experiment aims at:

    • A deeper understanding of the subject and improvement of technical expertise;
    • Identifying strengths and weaknesses of functional languages and open source projects in trading systems development.

    This article presents the motivational part and task decomposition.