Skip to content
View viplct's full-sized avatar

Block or report viplct

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.

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
viplct/README.md

Pham Duc Long

Solution Architect · 13+ years · Germany 🇩🇪 & Vietnam 🇻🇳

I turn ambiguous business problems into pragmatic architectures — clear boundaries, defensible trade-offs, and systems that scale without over-engineering.

Portfolio LinkedIn Email


🧭 About

  • 🏗️ Solution Architect shipping resilient, multi-domain systems — from on-chain analytics to booking engines, marketplaces, logistics and AI automation.
  • 🎯 I optimize for the right trade-off, not the trendy one: I distribute only when a single node genuinely can't cope, and I make every architectural decision defensible with an ADR.
  • 🌐 10+ domains, 20+ projects, 10+ clients across Germany and Vietnam.
  • 📚 Currently deepening data-intensive-systems fundamentals in public — see Labs below.
  • ☁️ AWS-certified · PSM I · comfortable from database internals up to org-wide platform strategy.

🛠️ Architecture Toolbox

Architecture & Data

Event-Driven Microservices Multi--Tenancy OLTP%2FOLAP PostgreSQL Redis Kafka DuckDB

Cloud & DevOps

AWS Docker Kubernetes CI%2FCD Terraform

Languages & Frameworks

TypeScript PHP Laravel Node.js NestJS React Python


🧪 Solution Architect Labs

Small, runnable repos where I work through core data-intensive-systems trade-offs. Each ships with an ADR (the reasoning) and a measured result (not just a claim).

Lab What it demonstrates Status
oltp-to-olap-pipeline Row-store vs column-store, star-schema modelling, and what ETL is really for — with a benchmark you can reproduce ✅ Live
storage-compute-separation Cloud-native storage/compute split, with a cost model showing when it's cheaper than a coupled DB — and when it isn't ✅ Live
scale-up-before-out Measuring how far a single node goes before you pay the distributed-systems tax 🔜 Planned
privacy-by-design-reference GDPR data-subject rights (access, erasure, portability) as an architecture concern 🔜 Planned

📖 Companion write-ups live on longpham.tech/blog.


📜 Certifications

AWS Certified PSM I DevOps ServiceNow


📊 GitHub Activity

Top Languages

GitHub Streak


Designing systems that are simple on purpose.longpham.tech

Pinned Loading

  1. oltp-to-olap-pipeline oltp-to-olap-pipeline Public

    Runnable lab: Postgres (OLTP, row-store) → ETL → DuckDB (OLAP, column-store) star schema, with a benchmark measuring the row-vs-column trade-off. Part of my Solution Architect labs.

    Python

  2. storage-compute-separation storage-compute-separation Public

    Runnable lab: storage/compute separation on MinIO + DuckDB, with a scenario-based cost model showing when cloud-native separation beats a coupled database — and when it doesn't. Part of my Solution…

    Python