BoopBoo

BoopBoo

0-day streak
DEVELOPER DATING APP PROGRESS UPDATE #3 So, after a lot of thinking I have came up with how I will structure my database and user system. I will be using SQL for generical storage, along with Redis Clusters for Caching. For the caching, after much deliberation, research and planning, I have come to the conclusion that 3 Masters and 2 Slaves per master would be the best for the scalability of the app, while providing low network latency and optimal speed. There is not too much to say other then the systems where designed using the flowcharts attached, some messy, some good. I would say them with words. But here are the charts. "Flowcharts speak louder than antisocial yapping in text" - Yoda source, trust me bro
https://scrapbook-into-the-redwoods.s3.us-east-1.amazonaws.com/a98047db-d75b-401d-9cd7-12c9b062ab20-createaccount.drawio.pnghttps://scrapbook-into-the-redwoods.s3.us-east-1.amazonaws.com/99f5f07b-0205-459c-bad0-f4c9105fb8d6-redis4iwannakmsdss.drawio.pnghttps://scrapbook-into-the-redwoods.s3.us-east-1.amazonaws.com/8344e729-40b9-4243-96e7-cd13bd719a0d-untitled_diagram.drawio.png
After looking though more advanced Redis and how it works for my systems. I have thought of a way to use Redis Clusters in order to better store my Cache in case a single node fails. Using this system will be even more complicated but I am finishing writing the flowchart and flows of the application.
https://scrapbook-into-the-redwoods.s3.us-east-1.amazonaws.com/a0439160-bdd9-430a-8782-ecba62d4e885-1_p8e3ks4denuf0s1igbqeia.webp
Here I am again with another entry, I worked on designing a flowchart and the system for the login. I think the chart can explain it's self, but it has a little bit on onboarding, and starts to introduce user sessions, caches and verifying GitHub Application Authentication.
https://scrapbook-into-the-redwoods.s3.us-east-1.amazonaws.com/7a421c93-fbbe-4bac-ba5f-1dd95c85d3c6-signuplogin.png
Developer Dating App Progress: So far I have been able to make the backend in express.js, along with Socket.io for the chat functionality. As of right now we are using passport to authenticate users with GitHub, and storing it to an MySQL database, along with for message history. For the pages we have a home page, a dashboard witch will be changed into a settings page on the profile page. The profile page is dynamic and works with any profile. Along with the search page witch currently has sliders but will soon be adjusted to work with location when we switch to mobile app functionality later. The current template frontend is in EJS as of right now, and we will keep it that way as for a web application for the beta, but I have plans to switch to React Native later. In the end unsure how to proceed. If you have any questions please make a thread.
https://scrapbook-into-the-redwoods.s3.us-east-1.amazonaws.com/2d68d28b-1bc0-4a9d-9f57-b83a2d011cfb-3232.pnghttps://scrapbook-into-the-redwoods.s3.us-east-1.amazonaws.com/a8f947a1-4a60-4db2-a738-cad809c34e24-fdfd.png
github emoji
js emoji
react emoji
Comp Sci Compass (Day 1) Today I got a mock version of the backend using express.js, along with a simple SQLite database. I started working on the front end using React. I was thinking of a terminal style design for navigating the page to have the application stand out some more. Thinking of switching to a database like Firebase, even though it is a no SQL database, it is built for Node.js/JavaScript and using JSON. I am thinking about it but I feel like I will stick with an SQL based database as I am storing a lot of reviews and more, along with courses connected to colleges/high schools. Here is a preview of the front end, the backend and database are mostly made. yes the console is working, to lazy to post a gif
https://scrapbook-into-the-redwoods.s3.us-east-1.amazonaws.com/bb49c994-2d93-4a0f-8d05-b6ac6b3c2c07-2024-12-02_10_41_57-.png