• Backend Systems • Real-World Engineering

Systems that
don’t break

I build backend systems that survive real-world chaos — retries, failures, race conditions, and unpredictable scale. Focused on reliability, clean architecture, and solving problems that actually show up in production.

Featured

Corrdex

Work Without Collisions

What it is

Corrdex is a web-based developer coordination platform that connects codebases to active tasks, claimed workspaces, and team rules so engineers can avoid collisions and validate changes before shared code breaks.

Why I’m building it

Most developer tools still focus on code search, chat, or static repository context. They do not track who is actively changing what, how work maps to tasks, or whether a push conflicts with team expectations. I think modern development needs coordination and validation, not just better lookup.

What makes it different

Corrdex combines semantic code understanding with task tracking, workspace claims, rule enforcement, and push-aware validation in one web workflow. The goal is to help teams work in parallel in the same codebase with less overlap, less ambiguity, and fewer regressions.

Key Engineering Highlights

  • check_circleBuilt a web-based developer coordination platform that links codebases, active tasks, and claimed workspaces to prevent collisions before code breaks
  • check_circleEngineered repository indexing and semantic analysis pipelines that process 8,000 files in under 3 minutes to power rules, docs, and workflow validation
  • check_circleBuilt push-triggered, task-aware validation flows that connect branches, tracked functions, and team rules for pre-merge change verification
  • check_circleDesigned architecture-aware rule enforcement and workflow documentation systems with scoped context generation across large codebases
  • check_circleBuilt task-aware workflows that connect code changes, ownership, and validation so teams can coordinate work directly inside the product
Role
Creator @ Cabunion & Corrdex
Focus
Backend Systems • Reliability • Distributed Design
Core Work
Payments • Concurrency • Data Ingestion
Stack
Node.js • TypeScript • PostgreSQL • MongoDB • Redis • Kafka • Expo
Infra
AWS • Azure • Supabase • Cloud Services

Built in production, not theory.

Most systems look good until real users hit them. Payments fail, APIs break, retries collide, and edge cases pile up. That’s where I work.

I focus on backend systems that deal with reality — concurrency issues, distributed workflows, third-party failures, and scaling without losing control. Clean code matters, but surviving production matters more.

Stack & Methodologies

Core Tech

  • TypeScript / Node.js
  • Next.js / React Native / Expo
  • PostgreSQL / MongoDB / Redis / Supabase
  • AWS (EC2, S3, SES, SQS, IAM, Aurora)
  • Azure (Blob, Communication, Event Hub)

Focus Areas

  • System Design & Architecture
  • Multi-Tier Data Ingestion
  • Concurrency & Retries
  • Payments & Real-world Edge Cases
Case Studies

Selected

Works

Volume 01 / 2026
01

Payment Retry Engine

Fault-tolerant retry system for handling failed transactions.

east

Problem

Handling duplicate payments, retries, and race conditions while ensuring no double refunds or payouts.

Approach

Designed idempotent workflows with controlled retries, state tracking, and database-level safeguards. Integrated with unreliable third-party PSP APIs.

Outcome

Eliminated duplicate transactions and stabilized payment flows under concurrent load.

02

Trip Processing System

Distributed backend for managing trip lifecycle with consistent state across services.

east

Problem

Concurrent requests and distributed updates causing inconsistent trip states during high traffic.

Approach

Implemented Saga-based workflows to manage multi-step trip operations with eventual consistency and controlled state transitions.

Outcome

Reliable trip lifecycle management with reduced inconsistencies under concurrent load.

03

Realtime Chat System

Thread-based chat system powered by Supabase realtime.

east

Problem

Managing multiple chat threads with real-time updates and consistent state across devices.

Approach

Built a scalable chat architecture using Supabase realtime subscriptions, optimized thread handling, and local persistence.

Outcome

Reliable real-time messaging with clean thread management and low latency.

04

Notification Processing System

Scalable push notification system with controlled delivery and rate limiting.

east

Problem

High volume of notifications causing rate limits, delivery failures, and inconsistent user experience.

Approach

Built queue-based processing with background jobs and rate limiting to ensure reliable and controlled notification delivery.

Outcome

Improved reliability and delivery success of push notifications under load.

05

Multi-Tier Data Ingestion Engine

Complex data pipeline syncing large codebases from local IDEs to the cloud.

east

Problem

Transferring massive Abstract Syntax Trees (ASTs) and architecture data from a client's machine to the cloud reliably without timing out or blocking the user.

Approach

Engineered a three-tier architecture: a VS Code extension, a local background daemon for parsing, and a highly optimized Cloud Server pipeline (S3 syncing).

Outcome

Drastically reduced payload sizes and eliminated API gateway timeouts, enabling seamless background syncing of massive codebases.

Experience

Work

History

Real Systems / Production

Creator & Lead Engineer

Cabunion

2025 — Now
east

Building and scaling backend systems for real-world travel operations, including payments, trip lifecycle management, and reliability under unpredictable production conditions.

Highlights

  • • Designed fault-tolerant payment retry system handling concurrency, idempotency, and edge cases
  • • Built trip lifecycle system using Saga-based workflows to manage distributed state with eventual consistency
  • • Developed push notification system with queue-based processing, rate limiting, and background jobs
  • • Integrated real-time chat using Supabase subscriptions
  • • Handled production issues involving retries, failures, and race conditions across systems
Node.jsTypeScriptPostgreSQLMongoDBExpoKafkaSupabaseAzure -BlobAzure -Communication ServicesAzure -Event Hub

Backend / Full Stack Developer

Impresiot

2023 Dec - 2024 Feb
east

Built an event management and ticketing platform end-to-end, including event creation, ticket booking, payments, and user engagement features.

Highlights

  • • Implemented ticket booking system with concurrency considerations
  • • Integrated payment workflows for event transactions
  • • Built email notification system for confirmations and updates
  • • Designed creator-follow system for user engagement
Next.jsNode.jsTypeScriptMongoDBPayment Gateway
Featured Project

Dev Competitive

Platform

(LeetsClub)

Group-based coding competition platform integrating LeetCode and GitHub. Built to drive consistency through peer competition and real-time progress tracking.

Next.jsTypeScriptMongoDBRedis
north_east

Problem

No unified way for developers to track progress, compete with peers, and stay consistent across platforms like LeetCode and GitHub.

Approach

Built group-based leaderboards, integrated external data sources, and enabled real-time tracking of coding activity.

Outcome

Created a competitive environment that encourages consistency and peer-driven motivation among developers.

Challenges

  • • Syncing GitHub and LeetCode data reliably
  • • Handling inconsistent external API responses
  • • Designing fair ranking logic across users
  • • Maintaining real-time leaderboard updates

Key Decisions

  • • Focused on private group competition instead of global ranking
  • • Used aggregated scoring instead of raw metrics
  • • Separated data ingestion from display layer

Learnings

  • • Strong core loop matters more than feature count
  • • Retention is harder than building
  • • Clear positioning defines product success