Deliverables Phase 3

Phase 3 Deliverables:

Continuing the development of the snack bar software, we will implement the following improvements and changes:

1. Implement an API Gateway and a serverless function for customer authentication based on CPF (Brazilian ID):

   • a. Integrate with the authentication system to identify the customer.

2. Implement CI/CD best practices for the application, segregating the code into repositories, for example:

   • a. 1 repository for the Lambda function.
   • b. 1 repository for the Kubernetes infrastructure using Terraform.
   • c. 1 repository for the managed database infrastructure using Terraform.
   • d. 1 repository for the application running on Kubernetes.

3. Repositories should have automated deployment to the cloud account using actions. The main/master branches must be protected, not allowing direct commits. Always use pull requests.

4. Improve the chosen database structure, document it following data modeling standards, and justify the database choice.

5. You are free to choose any cloud infrastructure, but you must use serverless services: functions (e.g., AWS Lambda, Azure Functions, or Google Functions), managed databases (e.g., AWS RDS, Azure Database, or Cloud SQL on GCP), and authentication systems (e.g., AWS Cognito, Microsoft AD, or Google Identity Platform on GCP).

Delivery artifacts:

• PDF with the link to the public repository or with access for the instructors. This repository must contain all the code (including Terraform and CI/CD actions).
• PDF with the URL of a video explaining the infrastructure used in the chosen cloud. In this video, the student should explain the function of each service and how it was set up.