Prerequisite: Read Part 12 — Vetting Senior Go Engineers in Vietnam and Part 13 — Magento Migration Cost Model.

Managing Vietnam Engineers Through a Magento Migration (2027 Remote Operating Model)

Answer-first: Successfully managing a remote engineering squad in Vietnam (GMT+7) from North America or Western Europe requires converting the 11-to-15 hour timezone difference from a communication hurdle into a competitive 24-hour Follow-The-Sun development engine. By establishing an Asynchronous-First Governance Model—anchored by version-controlled Architecture Decision Records (ADRs), a daily 90-minute synchronous overlap window (08:00–09:30 VN / 17:00–18:30 PT), and automated CI/CD shadow testing gates—engineering leaders eliminate blocked workflows and sustain rapid delivery cadence.

1. The 24-Hour Follow-The-Sun Development Loop

The 12-hour timezone inversion ensures continuous, round-the-clock progress when workflows are structured properly:

sequenceDiagram
    autonumber
    participant Onshore as Onshore Architect / PM (US Pacific: GMT-7)
    participant Git as GitHub & ADR Registry (Async Hub)
    participant Vietnam as Vietnam Core Go Squad (Vietnam: GMT+7)
    participant CI as Automated CI/CD & Shadow Test Env

    Note over Onshore,Vietnam: Phase 1: Overlap Window (08:00 - 09:30 VN / 17:00 - 18:30 PT)
    Onshore->>Vietnam: Sync standup, clarify domain specs, unblock PR reviews
    Vietnam->>Onshore: Demo completed service extraction & CDC metrics

    Note over Vietnam,CI: Phase 2: Vietnam Core Execution (09:30 - 18:00 VN)
    Vietnam->>Vietnam: Develop Go microservices, implement unit tests
    Vietnam->>CI: Push branch, trigger shadow traffic validation
    CI-->>Vietnam: Verification report (P99 latency < 45ms, parity 100%)
    Vietnam->>Git: Submit PR with ADR link and Loom video walkthrough

    Note over Onshore,Git: Phase 3: Onshore Daytime Review (09:00 - 17:00 PT)
    Onshore->>Git: Review PRs, execute acceptance sign-off, merge to main
    Onshore->>Git: Publish new RFC specifications for next service extraction

2. Codifying Architecture via Architecture Decision Records (ADRs)

To prevent misunderstandings and costly refactors across timezones, all technical decisions are formalized as version-controlled ADRs stored directly in the repository at docs/adr/:

# ADR-014: Transactional Outbox Pattern for Order Checkout Event Publishing

## Status
Accepted (Signed off by US Architect & VN Tech Lead on 2027-02-15)

## Context
During checkout migration, persisting the order record in PostgreSQL and emitting an 
OrderCreated event to Apache Kafka must be strictly atomic. Direct dual-writes produce 
inconsistent inventory states when Kafka broker network partitions occur.

## Decision
We mandate the Transactional Outbox Pattern using Debezium PostgreSQL CDC Connector:
1. The Go order-service writes the order entity and outbox event table in a single DB transaction.
2. Debezium captures WAL changes from `order_outbox_events` and streams to topic `orders.events.v1`.
3. Kafka retention is configured to 7 days with compact cleanup policy.

## Consequences
- Positive: Zero ghost orders or orphaned Kafka events during network drops.
- Negative: Adds 15ms end-to-end event propagation latency to downstream notifications.
- Compliance: Must include test coverage verifying database rollback cleans outbox entries.

3. The 48-Hour Production Cutover Protocol

Production cutovers are never conducted on hope. The migration squad conducts at least three end-to-end rehearsal drills in staging before executing final traffic cutovers:

flowchart TD
    StartCutover["T-24h: Freeze Legacy Magento Schema Changes"] --> SyncAudit["T-12h: Final CDC Offset Verification & Checksum Audit"]
    SyncAudit --> ParityCheck{"Replication Lag < 100ms & Parity = 100%?"}
    
    ParityCheck -- No --> AbortGate["Cutover Aborted: Resolve CDC Bottlenecks"]
    ParityCheck -- Yes --> TrafficShift["T-0: Cloudflare Envoy Weight Shift (10% -> 50% -> 100%)"]
    
    TrafficShift --> MetricsGate{"Error Rate < 0.01% & P99 Latency < 45ms?"}
    MetricsGate -- Fail --> AutoRollback["AUTOMATIC ROLLBACK: Revert Cloudflare Route to Magento 2"]
    MetricsGate -- Pass --> Decommission["T+4h: Lock Magento MySQL Writes & Finalize Cutover"]

Go/No-Go Decision Criteria Matrix:

1. Data Consistency: Checksum parity between PostgreSQL extracted tables and Magento MySQL master must reach 100.000% across a sample of 100,000 active SKU records.
2. Replication Lag: Debezium Kafka consumer group lag must remain under 50 records during simulated peak traffic.
3. HTTP 5xx Error Budget: Error rates must not exceed 0.01% (1 in 10,000 requests) over a consecutive 60-minute window.
4. Latency Ceiling: P99 response time for POST /api/v1/cart/checkout must remain below 120ms under 5x projected peak concurrency.

4. Weekly Governance Rhythm & Team Dynamics

A high-retention engineering culture bridging international headquarters and Vietnam talent relies on radical transparency:

• Async Daily Standups: Posted in Slack by 09:15 GMT+7 answering: (1) What shipped yesterday with PR links; (2) Today’s commit goal; (3) Blockers requiring onshore review.
• Code Review Turnaround SLA: PRs submitted before 17:00 GMT+7 receive reviews by onshore architects before 10:00 PT, ensuring zero idle waiting time.
• English Communication Standards: All technical documentation, PR descriptions, issue trackers, and ADRs are strictly in English. Code comments adhere to standard Go doc guidelines (godoc).
• Quarterly In-Person Kickoffs: Sponsoring onshore tech leads to visit Ho Chi Minh City or Da Nang for in-person sprint kickoffs dramatically deepens trust and domain alignment.

Frequently Asked Questions