On June 4, 2026, the curriculum transitioned from local scripts to network-connected architectures. We demystified APIs, request/response cycles, and JSON data formats.
1. Understanding APIs & Network Requests
We explored APIs (Application Programming Interfaces) as standardized protocol messengers enabling decoupled software systems to communicate. We compared the client-server request/response cycle to a restaurant, where the customer acts as the client, the waiter as the API gateway, the kitchen as the backend database, and the food as the delivered payload.
2. JSON Serialization & Schema Design
We analyzed JSON (JavaScript Object Notation) as the universal data exchange standard of web services. We mapped JSON structure to Python Dictionaries and Lists, noting its lightweight syntax, reliance on string double-quote keys, and strict data type values. This allows different runtimes to easily exchange messages and state.
3. Asynchronous Chatbot & Backend Frameworks
For our major project, Rashmi assigned a chatbot task utilizing the Gemini API, introducing Flask and FastAPI as backend frameworks. While the cohort struggled with JSON formatting, Divy and I created separate projects to implement the chatbot. I developed an asynchronous, type-safe FastAPI microservice. Using Pydantic for request validation, uvicorn for hosting, and the official Gemini API, I built a fully operational endpoint. Rashmi tested my chatbot and was deeply impressed by my dev speed and enterprise architectural choices.