👨‍💻 Backend Engineer & Systems Thinker
I build backend systems with a focus on predictability, explicit boundaries, and code that reads like it explains itself—simple by choice, not by limitation.

⚡ I cut my teeth in the cloud-native ecosystem contributing to the CNCF (Linux Foundation) as an LFX Mentee.
🙋‍♂️ I enjoy sharing what I learn along the way and helping others reason about distributed systems more clearly.

I'm a "forever Go" developer drawn to the cloud-native ecosystem.
I evaluate system design through the lens of:

• Strict Bounded Contexts: enforcing contracts so domains never leak.
• Predictability over Magic: strong typing, explicit dependency injection, and graceful degradation.
• Enterprise Observability: treating distributed tracing and structured logs as core application features, not afterthoughts.
• Preventive Design: designing things right so they don't become painful at 3:00 AM under heavy load.

Subscription Management Service A production-grade Go backend built to demonstrate strict domain boundaries and resilient infrastructure.

• Observability & Tracing: 100% instrumentation coverage (Metrics, Structured Logs, and Traces) across HTTP handlers, Redis, MongoDB, and Asynq. Features native W3C trace context propagation natively bridging the Queue-to-Worker event boundary.
• Adversarial Testing: Defense-in-depth test suite utilizing Testcontainers, pre-poisoned database decoys, and mutation-preventing domain tests to mathematically verify queries.
• Resilience: Implemented fail-open Redis rate limiting to prioritize core API availability during cache degradation.

I occasionally write about infrastructure and my open-source learnings.

• How I Passed the CKA Exam on My First Attempt
• My LFX Mentorship Experience with OpenELB (CNCF)

Backend & Systems: Clean architecture, domain-driven design, explicit state machines.

Observability & Data:

Cloud-Native & Tooling:

• Graceful Shutdown Topologies: Architecting deterministic, reverse-order shutdown sequences (via Dependency Injection graphs like uber-go/fx) to resolve connection-draining race conditions during SIGTERM.
• Task Chaining & DLQs: Decoupling domain mutations from external side-effects (e.g., separating billing logic from SMTP notifications) using Asynq task chaining and Dead Letter Queues.
• Caching Strategies: Expanding Redis implementations strictly for database query offloading and read-heavy endpoint optimization.
• E2E Verification: Expanding hermetic testing strategies into full End-to-End (E2E) request lifecycle verification.