search

sebastianbarry / Senior-Design-Capstone

Project Name: CUrPLAN
1 stars 0 forks source link

Do we want to "Re-write backend in Java (Prio = 1)"? #13

Open sebastianbarry opened 2 years ago

sebastianbarry commented 2 years ago

In the List of Items to add to the Program #7 as it stands currently, there is a task that exists as a priority 1 (very important):

Re-write backend in Java (Prio = 1)

  • Springboot
  • Retain front-end that they wrote
  • Have someone clean it up
  • Figure out database

This task brings up some points in my head that should be discussed by the team. Here are my opinions, thoughts and worries:

  1. This task is a very daunting, and challenging task. As both the backend and frontend code is currently written in ReactJS, intertwined together in the code, this task will require identifying which parts of the existing code are backend and frontend, splitting them, and integrating the new Springboot Java backend with our existing ReactJS frontend. Does this level of work merit being a change we want to spend time doing? (Think of this in terms of the expo presentation - is this a feasible thing we can "sell" to people at an expo? What problem are we trying to fix by doing this?)
  2. @CyR1en is the only person on our team who currently knows Springboot Java. This task requires the team to learn Springboot Java (which is a worthy accomplishment and a good thing to know), however if Ethan (being our spearhead in completing this Priority 1 task) is out for a week or something happens and we fall behind on this task, we will find ourselves very deep in a hole that we can't dig our way out of.

Here are our options as I see it:

  1. Accept the risks and possible reward, and continue to learn Java Springboot, and rewrite the backend in Java Springboot
  2. Accept the possible reward, but bet on a different MVC technology that we may understand more (such as Python Django) *still requires learning by everybody on the team, but not as much, and no one person to fall on with the task getting completed
  3. Deny this as an option, and maintain the ReactJS backend which has been built up by the previous Senior design team
sebastianbarry commented 2 years ago

We will discuss this during the 7/26 meeting, but please put any thoughts in this issue and think about it before the meeting

sebastianbarry commented 2 years ago

TO:DO