Java Full Stack Session 01 || IntelleQAcademy

Course Orientation and Expectations

The instructor introduced the Java full-stack course as a progression from fundamentals to practical, industry-style development. The course will focus mainly on backend development while covering enough frontend concepts to explain how the parts of an application connect.

Students were encouraged to ask technical questions, prepare topics assigned for later sessions, and stay consistent. The instructor said project information and learning management system (LMS) access would be provided as they became available. Class recordings would also be shared.

How the Internet and Web Applications Work

The instructor gave a simplified explanation of a web request: a user enters a domain such as flipkart.com, the domain is looked up to find an IP address, and the user’s device communicates with the relevant server.

A website was described as having three main parts:

• Frontend: The interface a user sees and interacts with, such as buttons, forms, images, and feeds.
• Backend: The server-side code that processes requests and applies application logic.
• Database: The system that stores information such as user details, posts, images, and messages.

A typical request flow works as follows:

1. A user action on the frontend triggers an API request to the backend.
2. The backend may read from or write to the database.
3. The backend returns a response for the frontend to display.

The instructor compared APIs to a phone number or bridge that lets one part of a system contact another. Different clients—such as a web browser, phone app, or desktop app—can use different interfaces while communicating with the same backend.

CRUD and API Methods

CRUD refers to four common kinds of data operations:

• Create: Add something new, such as creating an account or publishing a post.
• Read: Retrieve information, such as viewing products, messages, or a feed.
• Update: Change existing information, such as editing a profile or caption.
• Delete: Remove information, such as deleting a post.

The associated HTTP methods introduced were:

• POST — create.
• GET — retrieve.
• PUT — update.
• DELETE — remove.
• PATCH — update selected fields, though the instructor said the course would mainly use PUT.

Frontend actions—such as clicking a button or submitting a form—often trigger these requests. The backend contains most of the application logic, while the frontend presents the interface and calls the relevant APIs.

Further Topics Previewed

The course will later cover:

• System design, including latency, bandwidth, performance problems, and ways to improve applications under heavy traffic.
• Authentication, authorization, validation, Spring Security, and tokens.
• WebSockets, which support ongoing information exchange, such as chat.
• Low-level design (LLD) and high-level design (HLD), planned for after the foundational backend and security topics.

The instructor used preloaded videos in social-media feeds as an example of why some content may remain available briefly after a connection is lost.

Tools and Setup

Students were asked to install or prepare:

• Java for development.
• MySQL for the database.
• Git for source control and code commits.
• Postman for making and testing API requests without building a frontend.
• A Java IDE: Eclipse, Spring Tool Suite (STS), or IntelliJ IDEA.

The instructor recommended Eclipse or STS over VS Code for this course, particularly for Java debugging and development, while noting that Java can also be used in VS Code. Swagger was discussed as a tool for displaying API endpoints and testing them.

Project Guidance

Students will work on assigned projects, with the instructor teaching concepts and helping them plan their approach.

The instructor advised students to make Git commits regularly, even for small changes, rather than waiting until immediately before a review. Regular commits give reviewers evidence of ongoing progress.

Project evaluation may consider whether the work functions, whether it meets requirements, attendance, and commit history. Students were encouraged to try solving problems independently before seeking help if they remain stuck. The instructor also said AI tools could be useful and that guidance on using them would be provided.

Technical Clarification

The password discussion in the session loosely mixed up encryption and hashing. In standard practice, passwords are generally stored using a salted, one-way password hash. At login, the submitted password is hashed and verified against the stored hash rather than decrypted.

Speakers and Sources

• Instructor: The Java/backend course instructor; the name is not given in the subtitles.
• Students: Multiple students participated. Clearly identifiable names include Sachin (who asked about attendance tracking), Harshad (who asked about password storage), Gayatri, Vignesh, Ganesh, and Prabhu. Other students asked questions or responded, but their names or remarks are unclear in the auto-generated transcript.
• External sources and platforms mentioned: No formal outside speaker or source was featured. The instructor referred to Google searches, AI tools, YouTube class recordings, WhatsApp, and software tools including Postman, Swagger, Git, MySQL, and Java IDEs.