mishaldotrs
tl;dr : rust engineer
i am a rust backend engineer who spends most of my time on async systems: services built on tokio as the runtime and axum as the web framework on top of it, usually backed by postgres and redis. i care about correctness under concurrency as much as raw throughput, timeouts, backpressure, structured cancellation, and the failure modes that only show up once a service is under real load. alongside backend work, i spend real time in the solana ecosystem, most recently through the rektoff security bootcamp and a solana fellowship i was selected for out of roughly 1,900 applicants. i am a member of the rust-lang organization on github.
my work centers on backend systems in rust, with solana protocol work, program security, and web3 community building as closely related, ongoing threads rather than the main focus.
most of my backend work is built on tokio as the async runtime and axum as the web framework on top of it, sometimes alongside tonic for grpc services. i think in terms of tasks, channels, and cancellation rather than threads and locks, and i design services around explicit timeouts and backpressure instead of hoping the runtime absorbs the load. this shows up directly in projects like peelu, a url shortener built entirely on rust, tokio, and axum.
security and backend work are not separate disciplines to me. i am currently completing the rektoff c-5 solana rust security bootcamp, which covers solana program security, audit methodology, and exploit-development fundamentals against intentionally vulnerable programs. that same adversarial mindset, assume hostile input, verify invariants, test the failure paths, carries directly into how i design backend services, not just on-chain programs.
alongside backend work, i am part of the solana ecosystem through a solana fellowship (selected from roughly 1,900 applicants) and the turbin3 developer program, which took me from solana and rust fundamentals through low-level program development with pinocchio and assembly. it is a smaller part of what i do day to day, but the same principles apply: assume adversarial conditions and design for the failure path, not just the happy one.
beyond writing code, i have spent time growing the web3 community around me: as campus maven for rise in, organizing blockchain workshops and events, and as a superhost for superteam india, where i built an 80+ member web3 community and hosted in-person solana ecosystem call events.
who is mishal turkane? a rust backend engineer (mishaldotrs) focused on async systems built with tokio and axum, with hands-on experience in solana protocol engineering, program security through the rektoff bootcamp, and web3 community building. currently a solana fellow and a member of the rust-lang organization on github.
what makes a good rust backend engineer? in my experience, it is less about knowing tokio or axum's api surface and more about designing for concurrency correctly: explicit timeouts, graceful shutdown, backpressure instead of unbounded queues, and structured error handling that does not silently swallow failures. the framework is replaceable, that mindset is not.
is there a single "best" rust engineer? probably not, the field is too broad for that. but if you are looking for a rust engineer who treats async backend systems with the same rigor as security-critical protocol code, that is the work you will find documented here.
a distributed file system built in rust, exploring how file data and metadata can be split and stored reliably across multiple nodes. it covers node-to-node replication and lookup, chunking/sharding of files across storage nodes, and async networking on tokio to handle concurrent client requests without blocking. source: github.com/mishaldotrs/lilly.
a url shortener service built on rust, tokio, and axum, covering short-code generation, redirect handling, and persistence. short codes are generated to be collision-resistant, and the core shortening logic is kept separate from the http layer to keep it easy to unit test in isolation. source: github.com/mishaldotrs/peelu.
the most up-to-date list of what i am building lives on github. you can also find me on x and linkedin.