Ivan Rakov
Software Engineer at XTX Markets
London, England, United Kingdom
Summary
🤩
Rockstar🎓
Top SchoolIvan Rakov is a software engineer with nine years of experience building low-latency, JVM-based trading and distributed systems from London. He has led teams and shipped core features for high-performance projects—implementing transactional replication and persistence optimizations for Apache Ignite and designing a JVM trading engine and pricing models for OTC markets. Ivan’s open-source contributions to widely used projects like Apache Ignite and the OpenHFT suite focus on correctness, performance and low-latency serialization, including race fixes, benchmark additions and a notable SSD checkpoint speedup in production systems. He combines hands-on backend engineering with customer-facing professional services, having tuned Chronicle libraries to reduce marshalling costs and delivered connectors that cut latency versus proprietary solutions. Known for finding subtle concurrency and IO issues, he brings deep expertise in memory, serialization and trading domain models. His background from ITMO University underpins a pragmatic, research-informed approach to solving high-throughput systems problems.
9 years of coding experience
12 years of employment as a software developer
Master's degree, Computer Software Engineering, Master's degree, Computer Software Engineering at ITMO University
Russian, English
Github Skills (32)
caching10
transaction10
performance-monitor10
testing10
memory-management10
binary-format10
data-serialization10
distributed-systems10
queuing10
filelock10
java10
serialization10
apache-ignite10
javas10
performance-analysis10
Programming languages (3)
Github contributions (5)
apache/ignite
Jan 2017 - Aug 2020
Apache Ignite
Role in this project:
Back-end Developer
Back-end DeveloperContributions:133 commits, 117 PRs, 64 comments in 3 years 7 months
Contributions summary:Ivan primarily contributed to the core functionalities of the Apache Ignite project, with the majority of commits involving bug fixes and enhancements related to the cache and distributed systems components. Their work included addressing issues in atomic and transactional caches, fixing potential errors within the rebalancing process, and improving the overall stability and reliability of the system. These changes involved modifications across various Java source files, specifically within the core modules of the project. Further commits introduced support for the management and metrics of the persistent data storage.
data-management-platformin-memory-databasedistributed-sql-databaseapache-ignitenetwork-client
OpenHFT/Chronicle-Queue
Oct 2020 - Nov 2022
Micro second messaging that stores everything to disk
Role in this project:Back-end Developer
Back-end DeveloperContributions:7 reviews, 21 commits, 1 PR in 2 years 1 month
Contributions summary:Ivan implemented code generation for method readers, contributing to the core functionality of the Chronicle Queue library. They added a latency benchmark for method readers, demonstrating a focus on performance optimization and testing. Further contributions involved addressing issues related to cycle handling, padding, and thread safety within the queue's internal workings. The user also addressed a data race between read-only and read-write operations, strengthening the reliability of the queue.
storeseverythingpublisherchronicleartemis
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.