How anhdung2k1/contactless-checking works
• Backend API Service: Represent the “authentication” module (Spring Boot web service). Break it down into subcomponents such as:
• Controllers (e.g., AccountController, CustomerController, etc.)
• Service layers (interfaces and implementations for account, customer, notifications, tasks, and users)
• Security components (JWT filter, SecurityConfiguration, JwtService).
• AI/ML Face Model Service: Represent “face_model” as a separate service that runs the image recognition tasks and model training (with YOLOv11, FaceNet, ArcFace related scripts).
• Database Layer: Include MySQL as a relational database services container that stores user records, check-in logs, customer images, etc.
• CI/CD and Pipeline: A component for Jenkins (noting presence of Jenkinsfile and references to Jenkins in the README for triggering training pipelines).
• Infrastructure and Deployment: Show Kubernetes cluster components (e.g., pods for authentication, web client, MySQL, face model) and the Helm charts that orchestrate these deployments. Include Docker as the containerization platform.
• Additional DevOps Tools: Optionally denote the presence of Makefile (for build automation), Dockerfiles, and test harnesses (from the test/ directory).
Representing Relationships and Interactions
• From the Backend API, show interactions with the MySQL database (for CRUD operations) and AWS S3 (for storing and retrieving image files).
• Connection between the Backend and the Face Model service where images (or detection requests) are passed for facial recognition analysis.
Architectural Patterns and Design Principles
• A microservices architecture where services (authentication, face model, client, database) are separated into distinct containers.
• Security practices (JWT token-based authentication) and logging/aspects (LoggerAspect in the authentication service).
• Use of external configuration (application.yaml in Spring Boot, Helm values YAML files) to separate code from configuration, which is essential in cloud environments.
• That the system strongly leverages container orchestration (Kubernetes) for scalability and fault tolerance.