CST 489/499 Week 11 Learning Journal

-

 Milestones Accomplished

This week, my main contribution to our capstone project was to convert our data-fetching logic to use server-side rendering (SSR) instead of client-side fetching. Previously, I was using `useEffect` on the client to load data, which could expose sensitive information in our API calls. I refactored the logic by creating a server-side function that securely retrieves the data on the server and then passes it to the client component as props for rendering. This helps protect sensitive data and improves initial load performance.

In addition, I helped a team member implement authentication with Supabase. We successfully created a new account using Supabase Authentication and simulated logging in and out. 

Next Steps

My plans for next week are to update the database so that the Supabase Authentication table is properly linked to our User table. I also plan to revise the User table structure to focus on user-specific profile information rather than authentication-related fields such as email or password. Additionally, I will implement cookies and sessions to ensure that users can only access authorized pages.

Challenges

The challenge we are currently facing is the amount of work we have ahead of us to get a prototype ready for testing. We have been sorting many of the features as "stretch" features and focusing on what is absolutely necessary to test our algorithm. Our instructor, Dr. Feng, helped us focus on this at our last meeting.

Comments

Post a Comment

Popular posts from this blog

CST 438 Week 6 Learning Journal

-
Image
Compute as a Service An example of CaaS This week, we were assigned to read the chapter Compute As A Service from Software Engineering at Google . When the code is production-ready, it is important to find a compute service that will meet the organization's needs and follow best practices. Some best practices of a compute service include automation, workload types, data handling, and implementing distributed system concepts.  The first best practice for a service is to leverage automation. In this case, we are referring to handling failures such as container crashing or dealing with an unhealthy job or machine. Containers and machines should be used as "cattle" for services to be healthy, which means that when one crashes, another can pick up the job and continue forward.  The next best practice is handling different types of workloads. A service should be designed to handle batch jobs and serving jobs. Batch jobs are short-lived jobs that are split into small chunks by ...
Read more

CST 334 Week 1 Journal Entry

-
Image
Week 1: Introduction to Operating Systems One of the main topics that I learned about this week in CST 334 was operating systems and the role they play in running programs. Operation Systems have two main tasks. One of the tasks is to provide an abstraction layer to the user. This layer shields hardware information from the user, as the user should not have access to it. In addition to the layer of abstraction, the operating system also acts as a resource manager. It optimizes the use of the resources in a computer while allocating them to each program in a fair and equitable manner.  Both of these tasks are completed with the help of two modes provided by the CPU: kernel mode and user mode. While in user mode, the information about the hardware is hidden, and the user is provided an address space to do the intended job. This mode provides the user with access to user, application, and system programs. While in kernel mode, the administor has access to hardware and can change the m...
Read more

CST 370 Week 3 Learning Journal Entry

-
Image
 Brute Force Design Techniques and Divide-and-Conquer  This week, we learned about different exhaustive search algorithms that used a Brute-Force design technique. Exhaustive search algorithms consider every possible case before coming to a conclusion.  The first algorithm discussed was the sequential search and matching algorithm. This algorithm was presented in the form of searching a string to find a pattern, such as the one below. In this algorithm, every character in a string is checked for the pattern until the end of the pattern is reached. The efficiency of this algorithm is dependent on the text and pattern. In the example below, there are 16 characters in the text and 4 characters in the pattern that we are looking for. Since we are considering all comparisons and cases, we should have 13 shifts and 52 comparisons.  Another exhaustive search was conducted for combinatorics problems. An exhaustive search can be used to solve problems such as the Traveling Sa...
Read more