We are a tiny dev team compared to competition. All of us are working hard to build the best platform possible. The number of projects that we have in the works is growing so talent is always welcome ( careers@bitfinex.com ) Let's build an exchange technology for the P2P web!!https://twitter.com/bitfinex/status/1057243152283787269 …
-
-
Replying to @paoloardoino
To bad I already got a job. Would be great to help build a real exchange, not as a pet-project like during University. Super interesting field! Would you share teamsize and/or tech stack? Just curious.
1 reply 0 retweets 0 likes -
Replying to @mkuegi
We're 20 devs across the entire bitfinex, ethfinex, eosfinex and the other projects we have. Tech: Node.JS, C++, Mongo, MySQL, Linux, Redis and lot of stuff we built ourselves
1 reply 0 retweets 4 likes -
Replying to @paoloardoino
Thx for sharing. That's really quite small. C++ with MySQL for the matching engine, node with Mongo for web-backend? (I know, I'm super curious) How are the devs spread over the stack? Majority C++ or node?
1 reply 0 retweets 0 likes -
Replying to @mkuegi
Matching engine is not relying on MySQL, it would be too slow. We use ZMQ queues and it's all in memory. Most Node.js few C++ for hardcore stuff.
2 replies 0 retweets 5 likes -
Replying to @paoloardoino
Not relying on, but as a persisting layer? pure memory (without any persistence) sounds risky. Of course the matching itself would need everything in RAM for speed. So matching engine also (partly) node.js?
1 reply 0 retweets 0 likes
Indeed we have a persisting layer. Don't make me spoiler everything ;)
-
-
Replying to @paoloardoino
sorry ;) as i said, far too curious! thx for all the infos. All the best for the team being great while being small.
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.