Download source code:
git clone git@github.com:Fluidex/dingir-exchange.git ; cd dingir-exchange
- cmake
- librdkafka
# apt install cmake librdkafka-dev
run
cd docker
docker-compose upStarts the following containers:
- Kafka:
exchange_kafka - ZooKeeper:
exchange_zookeeper - PostgreSQL Timescale:
exchange_pq - Envoy:
exchange_envoy
Envoy is a service proxy and it's deployment area is displayed in the following, simplified architecture design:
(checkout overall Fluidex architecture here)
Fire it up:
make startall
See all the running processes:
make pgrep
4 processes should be running:
- matchengine
- restapi
- persistor
- tokio-runtime-w
Watch logs:
For once: make taillogs, continuously: make viewlogs
Shutdown the matching engine:
make stopall
As defined in docker/docker-compose.yaml, Postgres stores its data in the folder ./data/volumes/postgres_data.
Get into postgres container:
make conn
Show tables:
\d
You can run queries from there:
SELECT * FROM account;
From the project root, run:
make cleardb
If this doesn't work and you want to start with a clean slate, consider shutting everything down (make stopall, stop the docker containers) and remove the data directory:
rm -rf docker/data
Then start everything again (cd docker ; docker-compose up and make startall)
In the file src/matchengine/persist/state_save_load.rs the macro sqlx::migrate!() is called. By default, it will check out all the scripts that are in the migrations (only the root directory, subdirectories are being ignored), and run them against the db, in the order of the timestamps their filename starts with.
These migration scripts will mainly establish the database structure (tables, indexes, unique contraints, ...), but with the file migrations/20210223072038_markets_preset.sql it will also insert some data about the available assets and the available trading pairs.
There is a test suite written in TypeScript. It connects directly to the matching engine, over the matching engine's GRPC interface (it does not pass through Envoy or Kafka).
Install it:
cd examples/js ; npm i
and run it:
npx ts-node trade.ts
The test suite will work with a couple of data sets that are stored in different places.
They're stored in the file examples/js/accounts.jsonl.
The function setupAsset() in the file examples/js/trade.ts deposits funds onto user accounts.
The function orderTest() in the file examples/js/trade.ts creates an order and cancels it.
The function tradeTest() in the file examples/js/trade.ts creates orders that match and therefore result in a successful trade.
There is some dummy data in the file examples/js/config.ts too.