Software Engineer | Building Scalable & Distributed Systems
I work best where things get complex β
high-throughput queues, multi-service workflows, cloud architecture, and systems where one tiny mistake can wake you up at 3AM.
If something needs to scale, self-heal, or survive production chaos β
thatβs usually where I step in.
I build things that scale, tolerate failure, self-heal, and still look so elegant, just like a WOW.π
.
βββ βοΈ cloud_infrastructure
β βββ aws # Lambda, EC2, S3, RDS, SNS/SQS
β βββ gcp # Cloud Run, Pub/Sub, BigQuery
β βββ devops # Docker, CI/CD, Load balancers, Observability
β
βββ ποΈ backend_core
β βββ nodejs_ts # Event loops, workers, distributed queues
β βββ microservices # Async flows, idempotency, reliability
β βββ rust # Performance, memory-safety flex
β
βββ ποΈ persistence_layer
β βββ postgresql # Weird queries β clean query plans
β βββ cassandra # Write-heavy, planet-scale durability
β βββ mongodb # Document modeling done right
β βββ arangodb # Graph relationships
β βββ redis # Pub/Sub, caching, rate limits
β
βββ βοΈ web3_&_systems
β βββ solana # Parallel world of transactions
β βββ arduino_c++ # Sensors, signals, and soldering burns
β
βββ π scripting
βββ python # Automation, scripts, data pipelines[status]
online = true
game = "Call of Duty"
music = "Hard Techno" # BPM > productivity
[connect]
linkedin = "https://www.linkedin.com/in/sunanda35"
twitter = "https://x.com/0xSunanda"βSystems fail.
Great engineers design architectures that expect failure and still deliver.β
Reliability>Shiny ToolsPerformance>HypeArchitecture>ChaosClarity>Cleverness
I believe in idempotency, observability, retry logic, queues, caching, infra clarity, and clean boundaries.
Everything else is just flavor.
echo "Boot sequence complete. Systems optimal. Deploying next idea..."




