• Java 17 or later - SDKMAN - Recommendation
• Gradle 7.6.1 or later - Gradle build tool Installation
• Docker 24.0.2 or later - How to install Docker
• Docker Compose 1.29.2 or later - Reference guide
• The project runs on port 8096 (http://localhost:8096).

# Get the latest version

git clone https://github.com/lfneves/tech-challenge-hackathon.git

Check versions:

• Java 17+

  java --version

• Docker

  docker -v

• Docker Compose

  docker-compose --version

This is an example of how to use the software and how to install it.

./gradlew clean bootjar

In the main project directory:

Docker build and start applications:

$ docker-compose up --build

To recreate the application in case of problems, use the command:

$ docker-compose down

This document provides an overview of the architecture of the Punch The Clock system, designed to support user authentication, time registration, record viewing, and the generation of monthly reports.

The architecture is designed with a focus on performance, scalability, availability, security, data integrity, maintainability, and resilience. It utilizes AWS services to ensure scalability and high availability, and MongoDB Atlas as a cloud-based database solution.

• Description: Users interact with the system through a client (browser, mobile app, etc.).
• Responsibility: Initiate authentication requests, time registration, and record viewing.

• Description: An AWS service that acts as an entry point for backend requests.
• Responsibility: Route requests to corresponding services, manage traffic, authorization, and monitoring.

• Description: A container orchestration service that runs and manages containerized applications.
• Responsibility: Host and scale backend services, including authentication, time registration, and viewing.

• Description: Cloud-based MongoDB database service.
• Responsibility: Securely store and manage user data and time registration records.

The system uses best security practices, including:

• Secure authentication and session management.
• Encryption in transit and at rest.
• Policy-based access control.

Designed to handle high workloads, the system:

• Automatically scales with ECS Fargate to meet variable demands.
• Distributes traffic evenly with API Gateway and load balancing.

• Description: In-memory caching service.
• Responsibility: Speed up data access for frequently read data and reduce database load.

• Description: Message queuing service to decouple and scale microservices, distributed systems, and serverless applications.
• Responsibility: Manage task queues for asynchronous tasks, such as report generation.

• Description: A computing service that lets you run code without provisioning or managing servers.

Distributed under the MIT License. See LICENSE.txt for more information.