rezabrizi / exchange Goto Github PK

View Code? Open in Web Editor NEW

4.0 1.0 0.0 19.75 MB

Exchange with fast limit order book and custom server-client interface

CMake 1.29% C++ 98.71%

asio-library cpp hft hft-data hft-network hft-trading

exchange's Introduction

CPP is cool
algos are cool
food is cool
i will let you know once i find more

exchange's People

Contributors

Stargazers

Watchers

exchange's Issues

Clean up all files to include necessary prints to console only

Make it very test friend from the command terminal

For both the client and the exchange driver

Create a test file on how to test the program

Test

Providing database credentials
Adding clients
Adding instruments
Client connection (valid and non-valid clients)
Adding Orders (valid and non-valid orders)
Canceling Orders (valid and non-valid orders and clients)
Order Confirmation
Cancellation confirmation
Executions
Execution confirmation

Change LOB/Limits/Orders to use negative values for asks and remove bool

The current system uses a bool to identify bid or ask. Instead, the price sign should indicate if the order is bid or an ask. Bid is a positive price and ask is negative. The logic in all functions regarding LOB needs to be updated.

Save Orders and Executions to the database

Create a database driver class

Implement Cancel Order Function.

Return a list of order confirmations and execution confirmations when orders are added

Provide option for database connection credentials

The user should be able to specify what database they would like to use

OBM and the Exchange server use the database.

🚀 README.md needs more emojis 💪

Hello Team,

I've noticed that our README.md is quite informative and well-structured, but it lacks a bit of personality and visual appeal. I believe that incorporating more emojis can make it more engaging and easier to read, especially for new visitors to our project. Here are a few suggestions:

Introduction Section: Adding a welcoming emoji (👋) can make the introduction feel more friendly.
Features List: Each feature could be highlighted with a unique emoji that represents its functionality or benefit (e.g., 💡 for innovative features, 🛠 for tools, etc.).
Installation Section: A simple 🔧 or 📦 emoji can make this section pop and be more noticeable.
Contribution Guidelines: Encouraging contributions with a ✨ or 🤝 emoji could foster a more collaborative atmosphere.
Contact Information: Ending with a 📬 or 🤖 emoji might make the contact section more inviting.

Implementing these changes could enhance the readability of our README.md and make our project stand out more. I believe these small additions will go a long way in making our documentation feel more welcoming and engaging.

Looking forward to hearing your thoughts and any additional suggestions!

Design Classes

Classes and functionalities
Abstract Classes
Design Patterns

Asio
Net (Networking interface)