Skip to content

Architecture

Nate Zajac edited this page Oct 21, 2019 · 5 revisions

Architecture

  1. It will be SPA. It should be a very simple application that should be able to run using mostly client-side javascript. This should provide a faster experience for users of the web app.

  2. Main page: www.webevents.com (Place holder). We are waiting on the client to respond to see if he has any preferences.

  3. We are not using a REST API. In order to preserve the confidentiality of the users, we do not want to save states.

  4. Header, sidebar, file upload. The header will just be a title for the webpage. The sidebar will include the drop down to change the scheduling algorithm, and the resulting options that change based on the scheduling type. The file upload will be a interactive element where the user can upload the file, and it will change the state to show the different stages of the download/representation of data. In this picture, the header is located at the top of the screen. The sidebar is on the left side of the screen, and the file upload is in the middle of the screen.

  5. The database is only going to be used to push the data to the client. All of the work that the app is doing will be done client side.

  6. The app should not be making any requests from a database table, so we are not sure what queries there will be.

Clone this wiki locally