Skip to content
View nhatminh06's full-sized avatar

Highlights

  • Pro

Block or report nhatminh06

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
nhatminh06/README.md

Minh Pham

Computer Science and Mathematics student at the University of Minnesota, Twin Cities, interested in distributed systems, backend infrastructure, databases, networking, and AI systems.

I like building systems where correctness matters under concurrency, failures, retries, resource constraints, and real operational conditions. Most of my recent projects focus on understanding the mechanisms behind infrastructure rather than only assembling existing tools.

Areas of Focus

  • Distributed systems — consensus, replication, scheduling, leases, failure recovery
  • Backend and database systems — transactions, concurrency control, messaging, reliability
  • Systems programming — networking, storage engines, Linux, low-level debugging
  • Platform engineering — CI/CD, Kubernetes, GitOps, observability, infrastructure as code
  • AI systems — accelerator modeling, inference performance, ML infrastructure

Featured Projects

Project What I Built Focus
ForgeCI Self-hosted distributed CI engine with DAG scheduling, remote runners, PostgreSQL-backed job leasing, immutable source snapshots, artifacts, caching, durable logs, and native GitHub integration. Distributed systems, scheduling, concurrency, Go, PostgreSQL
PgSentry PostgreSQL reliability engineering lab for studying automatic failover, replication durability, network partitions, migration risk, backup recovery, and operational alerting using real multi-VM failure experiments. PostgreSQL, HA, distributed coordination, failure engineering
TensorForge AI accelerator performance-modeling toolkit for studying GEMM, Transformer, and Conv2D workloads across PE arrays, SRAM capacity, tiling strategies, DRAM traffic, and measured hardware performance. AI systems, computer architecture, performance modeling, Python
QuorumKV Distributed key-value store implementing Raft consensus, replication, snapshots, membership changes, ReadIndex, crash recovery, and real-process cluster testing. Consensus, distributed systems, Go
Wirestack User-space networking stack implementing TCP behavior including retransmission, adaptive RTO, flow and congestion control, NewReno, SACK, DNS resolution, HTTP, and Linux TAP interoperability. Networking, protocols, systems programming, C++
CommerceCore Correctness-first e-commerce backend exploring inventory contention, transactional checkout, idempotency, payment ambiguity, Kafka delivery, transactional outbox, reconciliation, and remote-service failures. Java, Spring Boot, PostgreSQL, Kafka, gRPC

More Systems Work

  • PageDB — educational database engine written in C with pages, buffer management, table storage, catalog, query execution, SQL planning, TCP protocol, and a Java client.
  • AEIGS — security-focused GitOps private cloud built with FluxCD, Kubernetes, Cilium, Kyverno, SOPS, Authentik, Prometheus, Loki, Grafana, and Hubble.
  • Linux Kernel Lab — custom Linux kernel environment with BusyBox, QEMU, kernel debugging, and character-device development in C.
  • MatchSense — real-time football analytics platform using Go, Python, Kafka, Redis, Kubernetes, GitOps, and distributed observability.
  • Market Pulse — analytical data platform built around Apache Iceberg, Trino, dbt, Airflow, Terraform, and MinIO.

What I Like to Study

A recurring question across my projects is:

What actually happens when the normal path stops being normal?

That has led me to experiment with:

  • concurrent transactions and race conditions
  • process crashes and restart recovery
  • network partitions and quorum loss
  • duplicate and reordered messages
  • stale distributed workers
  • ambiguous remote operations
  • storage durability and recovery
  • protocol retransmission and congestion
  • memory and compute bottlenecks
  • observability during real failures

I try to make those behaviors measurable through tests, failure injection, benchmarks, and reproducible experiments instead of describing them only at the architecture level.

Experience

  • DevSecOps Engineering Intern — VietinBank
  • Full-stack Engineering Intern — FPT Software

Technical Focus

Languages: Go, Java, C, C++, Python, TypeScript
Systems: Linux, TCP/IP, Raft, PostgreSQL, Kafka, gRPC
Infrastructure: Kubernetes, Docker, Terraform, FluxCD, ArgoCD
Observability: Prometheus, Grafana, Loki, OpenTelemetry, Jaeger
AI / ML: PyTorch, MLflow, accelerator performance modeling, model serving

Contact

Pinned Loading

  1. company-research company-research Public

    JavaScript 5

  2. nhatminh06 nhatminh06 Public

    Config files for my GitHub profile.

  3. market-pulse market-pulse Public

    End-to-end local data lakehouse platform for stock market analytics - MinIO + Apache Iceberg + Trino + dbt + Airflow + Superset

    Python 1

  4. linux-kernel-lab linux-kernel-lab Public

    Shell 1

  5. matchsense matchsense Public

    Event-driven football analytics platform with Go, FastAPI, Kafka, Redis, OpenTelemetry, Kubernetes, and GitOps.

    Go

  6. personal-cognitive-load-monitor personal-cognitive-load-monitor Public

    Educational MLOps platform for a synthetic cognitive-load classifier: FastAPI serving, DVC, MLflow, Docker, Helm, Kubernetes/GKE, KServe, Prometheus/Grafana, and Evidently drift monitoring behind a…

    Jupyter Notebook