First of all, hello everyone, I'm ilbey. I am developing a cryptocurrency exchange and I want to make a matching engine. I am thinking of building a system that can make faster transactions by keeping the transactions in memory. I am thinking of keeping the data in a noSQL database. I would appreciate if friends with knowledge can help.
1 Answers
Since this is an area I'm not very familiar with, the first thing I'd do is check Github for similar projects. I read the source code to understand their approach.
Blockchain is a different type of database than noSQL. What's the advantage of converting historical blockchain transactions to noSQL? Improve query performance, deal with varied blockchain transaction schemas, parallel processing of schemas across nodes. If you need these advantages along with an in-memory database, you might select one such as Tarantool (https://highscalability.com/how-to-choose-an-in-memory-nosql-solution-performance-measur).
Here's a curated list of blockchain projects: https://github.com/yjjnls/awesome-blockchain
Curated list of Crypto Exchanges: https://github.com/topics/cryptocurrency-exchanges?l=go
Crex is a Golang trading API that uses CSV or MongoDB (noSQL) https://github.com/coinrust/crex
