How ohaval/qr-code-generator-go-k8s works
Project type and purpose
• This is a cloud-native, full-stack backend service written in Go. Its sole responsibility is to expose a REST API to generate QR codes on demand.
• It’s containerized with Docker, supports local development on a kind Kubernetes cluster, and is production-ready for AWS EKS with auto-scaling and load balancing.
• The service is tested end-to-end (including load testing) and deployed via CI/CD workflows in GitHub Actions.
File structure
• Top level:
• main.go & main_test.go: the core Go application and unit tests
• e2e_test.go: integration/e2e tests
• Dockerfile & Makefile: build, run, test, docker commands, and deployment scripts
• go.mod / go.sum: Go modules
• scripts/: automation scripts for local and EKS setup/teardown
• k8s/: manifests split into kind/ (local) and eks/ (production)
• load-tests/: k6 performance tests
• .github/workflows: CI pipelines (lint, tests)
• Patterns & architectural clues:
• Single service binary (no separate frontend)
• Kubernetes manifests reflect micro-deployment: Deployment, Service, Ingress, HPA
• Docker multi-stage build, non-root user, health checks
README for additional insights
• Confirms:
• REST endpoints: health check, QR generate, root info
• Docker usage: dev vs prod images
• Local Kubernetes via Makefile + kind
• Production on AWS EKS: ECR registry, ALB ingress, HPA
• Testing strategy: unit, e2e, load tests via k6
• CI/CD automation via GitHub Actions
Detail
• Both local kind cluster (port-forward) and EKS cluster (ALB).
• Test tools (e2e_test.go, load-tests) as separate actors.
• Do not over-simplify—each script (setup-eks.sh, run-load-test.sh) can be noted as part of CI/CD or developer automation.