Week 11 Worklog

Week 11 Objectives:

• Conduct full end-to-end integration testing of the entire myFit application (all features, all screens).
• Write comprehensive project documentation — README, API reference, architecture overview.
• Clean up code, remove debug artifacts, and prepare the project for handoff.

Tasks to be carried out this week:

Week 11 Achievements:

• Integration Testing:
  • All backend API endpoints pass manual testing with valid and invalid inputs.
  • Docker Compose cold start reliable — API healthy within 25 seconds of docker-compose up.
  • Flyway V1, V2, V3 migrations run cleanly on a fresh PostgreSQL database.
  • All 6 user journeys tested end-to-end without critical failures.
• Documentation:
  • myFit-api/README.md covers full setup guide, environment variable reference, and all endpoint descriptions.
  • Frontend guide.md updated with navigation diagram, screen inventory, and AWS service configuration.
  • Architecture overview documented: Spring Boot API ↔ PostgreSQL ↔ AWS Cognito ↔ AWS S3 ↔ React Native App ↔ AWS Bedrock.
• CI/CD & Code Quality:
  • Implemented GitHub Actions workflows (.github/workflows) that automatically lint, test, build, and trigger rolling deployment updates to Amazon ECS Fargate upon merge.
  • Zero console.log or System.out.println remaining in production paths.
  • Automated TypeScript build (npx expo export) passes with zero errors in CI.
  • Automated Maven mvn clean package builds final JAR cleanly in CI.
• Project Retrospective — Key Lessons Learned:
  • IDOR prevention via JWT sub extraction is a critical security pattern that must be applied consistently throughout a user-scoped REST API.
  • Soft delete with @SQLRestriction is more user-friendly than hard delete for user-owned data — allows potential recovery.
  • Stateless JWT architecture eliminates server-side session complexity at the cost of token revocation complexity (addressed via forced logout + refresh queue).
  • React Native + NativeWind is a powerful combination — TailwindCSS-familiar syntax dramatically speeds up mobile UI development.
  • Redux + React Query separation of concerns works well: Redux manages auth/session state; React Query manages server cache and background refetching.

AWS Knowledge Learned:

• Performed a Well-Architected style review using the five pillars: Security, Reliability, Performance Efficiency, Cost Optimization, and Operational Excellence.
• Documented reliability posture through dependency health checks, backup and restore planning, and realistic RPO/RTO expectations.
• Applied a FinOps mindset by reviewing right-sizing opportunities, lifecycle policies, budget alerts, and idle resource cleanup.
• Consolidated a practical security hardening checklist covering IAM review, token policies, encryption coverage, secret handling, and audit logs.
• Prepared cloud runbooks for deployment, rollback, incident response, and routine operational validation.
• Defined handover readiness criteria such as reproducible setup, complete environment documentation, and explicit ownership boundaries.
• Built a forward AWS roadmap including ECS plus ALB hardening, CloudFront tuning, better observability, and staged production rollout.

In summary, week 11 turned the AWS topics learned during the project into an operational review and handover plan.

Next Week Plan:

• Final presentation to all stakeholders.
• Complete self-evaluation and feedback sections.
• Submit internship report.
• Celebrate project completion!