How prometric-testing/recruitment-assessment-sr-java-engineer works
Project type and purpose
• This is a sample microservices demo application comprising two Java-based modules—sample-api (an HTTP REST service) and sample-worker (a Kafka consumer/worker)—deployed on Kubernetes. It uses Docker for packaging, Terraform for cloud/infrastructure provisioning, and Kustomize/Kubernetes manifests for deployment to dev/qa/prod clusters.
File structure
• Top‐level modules:
• sample-api/ – Spring‐boot‐style REST API
• sample-worker/ – Kafka consumer worker
• Infrastructure-as-code:
• infra/terraform/ – cloud resource provisioning (e.g., VPC, EKS, ECR)
• infra/kubernetes/ – kustomize overlays and base manifests per environment
• Build & CI:
• Makefile – wrapper for Docker builds & kubectl commands
• GitHub workflows under .github/workflows for linting/tests/cache clearing
README for additional insights
• Describes end-to-end developer workflow:
• Build Docker images
• Push/ pull from ECR
• Apply Kustomize overlays → Kubernetes manifests
• Run in local Docker‐Desktop or remote clusters
• Debug via port‐forward and remote JVM attach
• Mentions Kafka topics and client utilities under the kafka namespace
• Component block is labeled with its module name and technology (e.g., “sample-api (Spring Boot)”).
• Environment overlays (dev/qa/prod) only if needed for clarity.
• Where secrets/config-env are injected (ConfigMaps, Secrets).
• Horizontal scaling/web-tier (HPA manifests) and autoscaling.
• End-to-end flow: code → Docker → ECR → Kubernetes → runtime.
• Make the dependencies explicit so new engineers can trace build, deploy, and runtime interactions at a glance.