$ whoami

Abeer Miglani

I write systems software in C++.

ECE undergrad at Shiv Nadar University. Right now I'm building a Redis-style server from scratch in C++; before that, Ripple, a simulator for how failures cascade through a city's infrastructure.

Open to SWE internships

Try cat redis or help in the terminal.

abeer@portfolio: ~interactive

Welcome to abeer@portfolio. Type `help` to get started.

abeer@portfolio:~$ now

building Redis-style server (5/10 milestones)

learning Rust

open to SWE internships

Projects

client → server · request 1 of 2

The request "hello1" is sent as a 4-byte length, 06 00 00 00 in little-endian order, followed by 6 payload bytes.

Sends two requests, hello1 and hello2, split into random TCP segments, and replays how the server reads them.

roadmap

5/10 done

  • Socket programming (done)
  • TCP server + client (done)
  • Binary protocol + framing (done)
  • Concurrent I/O models (done)
  • Event loop (done)
  • Key-value server (planned)
  • Hashtable (planned)
  • Sorted set + AVL tree (planned)
  • TTL expiry + timers (planned)
  • Thread pool (planned)

~/redis-cpp · Systems · ongoing

Redis-style server

A Redis-style TCP server in C++, built from first principles to understand how Redis really works.

  • TCP server and client written directly against POSIX sockets.
  • Length-prefixed binary protocol (4-byte header + payload) to frame messages over a TCP byte stream.
  • read_full / write_all loops so partial reads and writes never corrupt a message, with a 4 KB size guard.
  • Event loop over non-blocking sockets, so one thread serves many clients at once.
  • Benchmarked 25K requests per second, with 38 µs median and 82 µs p99 latency, over 100K loopback round trips.

what I learned

TCP delivers a byte stream, not messages: one read() can return half a request or two of them, so the protocol has to carry its own boundaries. The event loop changed the shape of the server: instead of blocking on one client at a time, one thread watches every socket and serves whichever is ready, so a slow client no longer holds up the rest.

C++ · POSIX sockets · Jul 2026 – present

Water plant 2 down → 4 waves, 5 of 9 down. Hospital lost in wave 4.

~/ripple · Manipal Hackathon 2026 · sole developer

Ripple

Simulates how one infrastructure failure cascades through a city's power, water, transit and telecom networks.

  • Rust (PyO3) extension for the all-pairs shortest-path hotspot, called 20+ times per recommendation request.
  • Motter–Lai overload cascade on an in-memory graph, streamed to the map wave by wave over WebSockets.
  • Recommendation engine that verifies every fix by re-running the cascade, ranked by failures prevented and hospitals kept online.

Rust · Python · WebSockets · Sep 2026

# earlier

About

Name

abeer — systems-minded software engineer

Synopsis

abeer [--cpp] [--c] [--learning rust] [--open-to internships]

Description

I'm a second-year Electrical and Computer Engineering student at Shiv Nadar Institution of Eminence, and most of what I build leans towards systems: sockets, protocols, graphs and the data structures underneath them.

Right now I'm building a Redis-style server in C++ from first principles, and learning Rust, which I've already used to speed up the hottest path in Ripple.

Education

Shiv Nadar Institution of Eminence

B.Tech, Electrical and Computer Engineering · Aug 2025 – May 2029 · Dadri, UP

Outside coursework: 140+ DSA problems on LeetCode, Codeforces, CodeChef, HackerRank.

Skills

--languages
C++CRust (learning)PythonSQLTypeScriptHTML/CSS
--frameworks-libraries
FastAPIFlaskReactCeleryNetworkXPandasSelenium
--databases
PostgreSQL + PostGISNeo4jRedisMySQL
--tools
GitDockerGitHub ActionsVS Code

See also

Get in touch

I'm looking for SWE internships. Email is the fastest way to reach me.