标签：used financial company months system C++ been Rust
https://www.reddit.com/r/rust/comments/bhtuah/production_deployment_of_rust_in_hft_system_at/
A Korean financial company runs a profitable HFT(High Frequency Trading) system with DMA(Direct Market Access) to KRX(Korea Exchange). We rewrote trading strategies and related code from C++ to Rust, and the system recently got deployed to production.
The project has been up for 16 months, the trading has been up for 10 months, it has been profitable for 9 months, Rust build integration has been set up for 10 months, trading strategy rewrite has been worked for 7 months, the final push took a month. The final push required Rust version beating (already quite optimized) C++ version in latency in all cases, even if it is just a little bit. This was achieved. (Although to be honest, it was actually achieved by switching active development to Rust and putting C++ version in maintenance mode.)
x86_64-pc-windows-msvc target is used with Visual Studio MSBuild based build system for release and x86_64-unknown-linux-gnu target is used with CMake based build system for CI. bindgen and cbindgen are used for C++ FFI. C++17 standard is used, with Visual Studio 2017 and GCC 8. Rust toolchain used is stable channel and immediately updated after the release. Cargo dependencies are locked and updated discretionally. vcpkg is used for C++ package management, both on Windows and Linux. CI was CircleCI 1.0 running on Ubuntu 16.04 LTS, but switched to CircleCI 2.0 with Docker with freedom from dealing with old versions. Deployment is automated by PowerShell Remoting.
Ask me anything, although I can't say I will answer anything. If you are interested in work, PM me. This is posted in the hope that it would be useful as a precedent, because we experienced such resistance first hand.
标签：used,financial,company,months,system,C++,been,Rust 来源： https://www.cnblogs.com/dhcn/p/12105487.html
本站声明： 1. iCode9 技术分享网（下文简称本站）提供的所有内容，仅供技术学习、探讨和分享； 2. 关于本站的所有留言、评论、转载及引用，纯属内容发起人的个人观点，与本站观点和立场无关； 3. 关于本站的所有言论和文字，纯属内容发起人的个人观点，与本站观点和立场无关； 4. 本站文章均是网友提供，不完全保证技术分享内容的完整性、准确性、时效性、风险性和版权归属；如您发现该文章侵犯了您的权益，可联系我们第一时间进行删除； 5. 本站为非盈利性的个人网站，所有内容不会用来进行牟利，也不会利用任何形式的广告来间接获益，纯粹是为了广大技术爱好者提供技术内容和技术思想的分享性交流网站。