Easier to think of a database = storage layer + data model + query layer (language + optimizer)
Easier to think of a database = storage layer + data model + query layer (language + optimizer)
Makes composition so much nicer to look at and reason about
Makes composition so much nicer to look at and reason about
I wrote a small blog post and I'll cover the high level points in this 🧵
I wrote a small blog post and I'll cover the high level points in this 🧵
Open to work in distributed systems/databases and backend positions. I have experience writing systems that implement different distributed consensus protocols.
Résume: resume.akshatsharma.xyz
Open to work in distributed systems/databases and backend positions. I have experience writing systems that implement different distributed consensus protocols.
Résume: resume.akshatsharma.xyz
My struct for my open addressing variant is an enum which occupies 24 bytes when u64 is used as key-value. Each cache line is 64 bytes which means 2-3 per line
My struct for my open addressing variant is an enum which occupies 24 bytes when u64 is used as key-value. Each cache line is 64 bytes which means 2-3 per line
Unfortunate because I was really enjoying using trait aliases
Unfortunate because I was really enjoying using trait aliases
- quit job to get into systems-y role
- picked up Rust
- wrote a small Raft implementation in Rust
- contracted with startup building ingestion engine for unstructured data
- wrote a small storage engine in Rust
- started working in systems-y role @Conviva
- read & wrote a lot
- learned a lot
- quit job to get into systems-y role
- picked up Rust
- wrote a small Raft implementation in Rust
- contracted with startup building ingestion engine for unstructured data
- wrote a small storage engine in Rust
- started working in systems-y role @Conviva
- read & wrote a lot
- learned a lot
web.stanford.edu/class/cs240e...
web.stanford.edu/class/cs240e...