How yazid0hakimi/azure-automation works
Project type and purpose
• This is a full-stack, microservices-based application hosted on Azure using a monorepo structure.
• It comprises:
• An Angular frontend (“angular-front/”)
• Spring Boot microservices (discovery, profile, employee-performance, gateway) in “spring-backend/”
• Kubernetes manifests in “k8s/” for deploying services to AKS
• Terraform infrastructure as code (“terraform-infra/”) to provision Azure resources
File structure
• Top-level directories correspond to major subsystems: frontend, backend, infra, and kube-configs.
• “spring-backend/” houses multiple Spring Boot modules, each with its own Dockerfile, application properties, controllers, services, repos, DTOs, and feign clients.
• “k8s/” organizes base manifests, overlays (dev, PBD/HPA), FluxCD configs, and monitoring (Grafana dashboards).
• “terraform-infra/” defines reusable Azure modules (AKS, ACR, SQL, key vault, networking, firewall, VM, bastion) and pipelines.
README
• Confirms a monorepo for coordinating frontend, backend, infra, and Kubernetes.
• Goal: unified development, testing, deployment across Azure.