Week 5: Learning Serverless and Forming the Backend Idea for GuardScript

1. Objectives

  • Study serverless architecture on AWS in more depth.
  • Evaluate how Lambda, API Gateway, and DynamoDB can be combined into a real backend system.
  • Brainstorm project ideas and identify a direction that matches the team’s implementation capacity.

2. Weekly Tasks Breakdown

DayMain TaskDetailsStatus
MonLambda Deep Dive- Studied the Lambda execution model, statelessness, cold starts, and Function URL.
- Evaluated how Lambda could serve as the backend runtime foundation.		Completed
TueAPI Gateway and DynamoDB- Explored API Gateway and DynamoDB from a query-pattern perspective.
- Studied partition keys, GSIs, and API-oriented data design.		Completed
WedHands-on Serverless API- Built a simple CRUD API in a serverless style.
- Validated backend feasibility without a traditional server model.		Completed
ThuProject Brainstorming- Joined team brainstorming around secure code distribution, licensing, and script management.
- Helped shape the initial idea of GuardScript.		Completed
FriPre-Tet Review- Consolidated the technical lessons learned from weeks 1-5.
- Prepared the thinking needed for scope finalization and backend design after the Tet break.		Completed

3. Outcomes

  • Built a solid technical basis for choosing a serverless direction for later deployment.
  • Validated how backend APIs can be implemented with Lambda and DynamoDB.
  • Formed a clearer product idea for GuardScript with identifiable backend core components.

4. Issues & Solutions

  • Issue: DynamoDB required a different design mindset compared to relational databases.
  • Solution: Approached schema design through expected query patterns first, then derived tables and indexes from those needs.

5. Next Steps

  • After the Tet break, return to finalize the scope of GuardScript.
  • Begin detailed backend architecture, API surface planning, and security flow design.