“Let’s solve hard backend problems together — the kind that keep your engineers up at night.”
👋 Who I Am
I am Lê Tuấn Anh (vesviet), a Senior Go Backend Architect and Distributed Systems Engineer with 17+ years of production experience. I have led the migration of a decade-old Magento monolith into a 21-service Go microservices ecosystem at zero downtime, designed APIs handling 25M+ requests/month at peak 8,000 RPS, and reduced p95 latency from 1.2s to 120ms through architecture and caching strategy.
I work with teams that need:
- Deep backend architecture expertise they cannot hire full-time
- An experienced engineer to guide critical migrations or scale decisions
- Honest technical review of a system under pressure
🎯 What I Can Help With
Microservices Architecture & Migration
- Strangler Fig migrations from PHP/Magento/Laravel monoliths to Go microservices
- Distributed data consistency: Dapr Pub/Sub, Transactional Outbox, Saga orchestration
- Service mesh design, gRPC/REST API gateway patterns
- Zero-downtime bidirectional data synchronization strategies
High-Traffic Platform Reliability
- Backend architecture for flash sales, peak-event traffic (8,000+ RPS)
- Database optimization: PostgreSQL sharding, Redis caching strategies, Elasticsearch indexing
- Kubernetes cluster design (EKS/K3s), horizontal scaling, and OOM/CPU profiling in production
- Goroutine leak detection, Go pprof memory and CPU profiling
GitOps & Developer Platform
- ArgoCD GitOps pipeline design for multi-service Kubernetes deployments
- CI/CD pipeline automation for Go microservices
- Secrets management, Helm chart design, and cluster upgrade strategies
Technical Architecture Review
- System design review and ADR writing
- Code review for Go microservices, performance bottleneck identification
- Architecture readiness assessment before major scaling events
💼 Recent Work (Selected)
| Project | Scope | Outcome |
|---|---|---|
| Lotte Innovate / Vigo Retail (2021–Present) | Monolith → 21 Go services, B2B/B2C Commerce | Zero-downtime migration, 40% checkout throughput improvement |
| SnapMart & ICM (2019–2021) | Magento 2 backend, Flutter mobile APIs | Payment gateway, fulfillment routing, warehouse scanner integrations |
| Composable Commerce Architecture | Open-source 21-service Go ecosystem | Dapr Pub/Sub + Outbox + Saga in production-grade Go |
View my full profile → | GitHub Portfolio →
🤝 Engagement Types
| Type | Description | Duration |
|---|---|---|
| Architecture Review | Deep review of your current system, migration plan, or scaling strategy | 1–2 weeks |
| Advisory Retainer | Ongoing technical guidance for your engineering team | Monthly |
| Hands-On Consulting | Direct implementation or lead engineering on a specific problem | Project-based |
| Workshop / Talk | System design deep dives, Go microservices best practices for your team | 0.5–1 day |
📍 Location & Availability
- Based in: Vietnam (UTC+7)
- Remote: Yes — globally available
- On-site: Vietnam and Southeast Asia
- Languages: Vietnamese (native), English (professional)
📫 Let’s Talk
The best starting point is a short conversation about your problem. No long forms.
- Email: vesviet@gmail.com
- LinkedIn: linkedin.com/in/vesviet
- GitHub: github.com/vesviet
I read every message and respond within 48 hours on business days.
FAQ
What does a Go backend architecture consulting engagement look like?
A typical engagement starts with a 1-week discovery phase (paid): I review your current architecture, codebase, and infrastructure configuration, then produce a written Technical Assessment document covering bottlenecks, risk areas, and a prioritized roadmap. From there, engagements take one of three forms: a 2-week Architecture Review (detailed ADR + migration plan for one specific problem), an ongoing Advisory Retainer (monthly fixed hours for architectural guidance, code review, and escalation support), or hands-on consulting (direct implementation on a specific migration or scaling problem). All engagements start with a 30-minute scoping call — no forms, no decks.
Can you help migrate a Magento monolith to Go microservices?
Yes — this is one of my primary specializations. I led the zero-downtime migration of a decade-old Magento 2 platform into a 21-service Go microservices ecosystem at Lotte Innovate / Vigo Retail (2021–present), using a 3-Phase Strangler Fig pattern with Debezium CDC, bidirectional Dapr Pub/Sub sync, and a hot standby period before final cutover. The approach produces zero data loss and maintains rollback capability throughout. Before engaging, I recommend reading The Zero-Downtime Blueprint: Moving from Magento to Microservices to understand the specific methodology and whether your platform’s complexity profile matches the approach.
Do you work remotely with international clients?
Yes. I am based in Vietnam (UTC+7) and work with clients in North America, Europe, and Southeast Asia remotely. My working hours can flex to overlap with UTC-4 to UTC+1 for regular meeting cadences. For clients in the same timezone (Singapore, Thailand, Japan, South Korea), overlap is immediate. Async communication (written specs, recorded architecture walkthroughs, Loom videos) is a first-class part of how I work — most clients find this more efficient than synchronous meetings for technical communication.
What is the minimum engagement size you take on?
The minimum effective engagement is an Architecture Review (1–2 weeks) because shorter engagements do not allow enough time to produce actionable technical output. I do not do hourly 1-hour sessions — they are too shallow to be useful for backend architecture problems. If you are unsure whether a full engagement is warranted, start with the 30-minute scoping call (free) where we scope the problem. If it is solvable with a written answer or a reference to an existing post, I will tell you directly rather than recommend an engagement.