01
Distributed systems
Queues, delivery semantics, recovery, and the contracts that keep remote systems dependable.
Distributed systems · Platform · Media
Building reliable systems between the edge and the cloud.
I’m Adarsh Mishra, a software engineer at Qube Cinema. I work at the boundary between remotely deployed systems and cloud services—distributed agents, observability, safe updates, and recovery.
I also build production media infrastructure across Go, Rust, C++, Linux, Kubernetes, GStreamer, and GPU rendering.
Current focus● active
edge-agent platform
Making remote software observable, recoverable, and safe to update.
System
distributed control
Signals
traces · logs · metrics
Runtime
Go · Linux · Windows
Rule
rollback is a feature
Working across/Distributed systems/Observability/Platform engineering/AI-assisted development/Media systems
The work
Hard systems, clear contracts.
I’m most interested in software that has to keep working through unreliable networks, partial failure, operational constraints, and long-lived deployments.
02
Cloud & observability
Kubernetes, OpenTelemetry, production diagnostics, and evidence-driven incident analysis.
03
Platform engineering
Safe updates, rollback, packaging, and services that survive real operating environments.
04
Media infrastructure
Secure playback, GPU rendering, and the systems behind modern digital cinema.
How I work
The operating principles.
01
Failure-aware by default
Design the recovery path at the same time as the success path.
02
Evidence closes the loop
Traces, tests, and production behavior matter more than a plausible explanation.
03
AI with engineering judgment
Use agents for leverage; use architecture and verification for confidence.
From the notebook