Go Core:

• Goroutines & channels — kapan pakai buffered vs unbuffered
• Context propagation — cancellation, timeout, deadline
• Error handling idioms — wrapping, errors.Is(), errors.As()
• Interface design — duck typing, small interfaces
• Testing — table-driven tests, mocks, benchmark tests

Microservices:

• Strangler Fig pattern — bagaimana decompose PHP monolith secara gradual
• Service boundaries — bounded context (DDD)
• Inter-service communication — gRPC vs REST vs event-driven
• Distributed transactions — saga pattern, eventual consistency
• Circuit breaker, retry, timeout — resilience patterns

Siapkan Code Walkthrough:

// Contoh: clean architecture structure yang akan ditunjukkan
cmd/
  server/
    main.go
internal/
  domain/        // entities, value objects
  usecase/       // business logic
  repository/    // data access interface
  handler/       // HTTP/gRPC handlers
  middleware/    // auth, logging, recovery
pkg/
  grpc/          // proto definitions
  config/        // viper config

Pertanyaan yang mungkin muncul:

1. "Bagaimana Anda akan decompose SIAKAD monolith?"

   • Jawab: Strangler Fig, mulai dari Auth Service (paling independen)
   • Gambar: API Gateway → route by path → old monolith / new service

2. "Bagaimana handle KRS race condition?"

   • Jawab: Redis distributed locking (Redlock), Go goroutines, queue system
   • Metrics: p99 < 200ms, zero overselling

3. "Design payment service yang ACID-compliant"

   • Jawab: Saga pattern, idempotent operations, audit trail
   • Reference: BTPN banking backend experience

AWS stack SEVIMA (dari riset):

• EKS (Kubernetes)
• RDS (PostgreSQL/MySQL)
• S3 (static assets)
• CloudFront (CDN)

Siapkan jawaban untuk:

• CI/CD pipeline design (GitHub Actions → Docker → EKS)
• Blue-green deployment strategy
• Monitoring stack: Prometheus + Grafana
• Log aggregation: ELK / CloudWatch