graphshard labexploring how placement, batching, caching, and shard communication affect graph workloads.
teaching databases to do things nobody asked for.
i'm 19, from india, building toward database infrastructure work, mostly distributed systems and the durable, low level stuff that decides whether a system actually survives a crash.
right now that's quorum loro gateway, a crdt sync server built on top of a quorum replicated durable log, and graphshard lab, a sharding prototype for graph workloads.
taught myself most of this by picking a real system, poking at its internals until something broke, then figuring out why.
write-ups
quorum loro gatewaybuilding durable crdt sync on top of a quorum-replicated log.