01 Utility and System Design – IPL Dashboard – Full Stack Net Improvement Tutorial



It is a sequence of movies that cowl full stack internet software the place we’ll be constructing a easy IPL dashboard app from the scratch. If you’re new, begin from the sequence introduction video right here: https://youtu.be/aL1oP4GJR7M

Collection Playlist: https://www.youtube.com/playlist?record=PLqq-6Pq4lTTa8V613TZhGq4o8hSgkMGQ0
GitHub Repo: https://github.com/koushikkothagal/ipl-dashboard

#JavaBrains #CodeWithMe #SpringBoot #React

source

39 thoughts on “01 Utility and System Design – IPL Dashboard – Full Stack Net Improvement Tutorial”

  1. Can you add more discussion on Dockerizing the Spring boot + MySQL as one single micro-service and how the Data loading could work if each micro-service is going to have it's own instance of MYSQL. It's just a scaling of the design you just spoke.

    Reply
  2. Koushik, I'm curious. What device are you using for drawing?

    As usual, I had great learning experience from your highly informative tutorials like these. This course is a smasher and exhibits your greatest teaching capabilities.

    Reply
  3. hello sir .one doubt,hot get the spring api message in react applicetion sir
    example :In spring boot I was Register some student info that was(succesfully inserted )in this response message
    how to show on react appllication

    Reply
  4. Your architectural considerations make sense as for the purpose of the tutorial probably it wouldn't make much difference an external database or an embedded one.
    However you're suggesting to parse & process the csv on startup; to do this you'll have to include the csv in every spring boot app instance. This choice is not optimal in my opinion. You're duplicating the data for every instance, it might be negligible since your entire dataset is relatively small. It also implies that your input (the csv) is a static resource part of the application. This causes a larger image size and in case you need ro update the csv with a newer version you'll have to rebuild the image. If you really wanna have embedded input I think it would be better to have the spring boot app download the file from a single external independent URI and the process it on startup. This will reduce the size of your docker image and make your app independent from the csv. Say tomorrow you need to spawn an instance with data of matches from 2020 until 2025, you don't need to recompile anything and you don't need to rebuild your image. Personally I still believe an external database would have many more advantages over this way.

    Reply
  5. I wish I came across this a few days ago. I am really looking forward to this.
    I am building my first app for a university project, really struggling with the login form.
    I am using CORS as react runs on port 3000 & Spring Boot on 8080, cors has been disabled.
    I am using fetch API at the front end, And using the traditional form system in the backend which redirects on success/failure.
    Works perfectly with a normal browser request but not from Javascript fetch.
    There is no proper debugging as I am not even seeing an error, just keeps redirecting to login as if login fails

    Reply
  6. You probably know the answer by now – but D/L is the Duckworth Lewis method. So if in case the match result is not achieved on the ground due to inability to conduct a full match, then the D/L method is used to decide the target score for the team batting second, in case or a curtailed match (due to a rain / other factors).

    Reply
  7. great design discussion.
    I have one doubt. As we are using an embedded database because we are not gonna write to the database so there will be no out of sync problem.
    but if we want to show ipl 2021 data then we have to download the updates csv file from Kaggle and have to copy that in our spring boot app and have to restart it our app. Am I right? please comment

    Reply
  8. "Google on the right and a developer on the left who has no idea what they're doing" – For a moment, I thought you're were rubbing into me 🤣 Got too personal there!

    Reply
  9. As the data gets populated to DB on startup, UI need to wait till all the data loads up. Due to this approach, the application will startup may happen slower. How we are going to handle this? In this application, currently data is less but what if data available from 1970 ~ now.

    Reply
  10. One concern i see with this approach, for data consistancy you have to rely on the csv file for all your application nodes. what if the file gets compromised after some time ? Wouldn't it be better to have a load balanced db instance with replication , even better to have distributed cache in between db and application?

    Reply

Leave a Comment