Versions Compared

Old Version 25

changes.mady.by.user Jasper Kooy

Saved on

compared with

New Version 26

changes.mady.by.user Jasper Kooy

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Architectural Overview


DNSThe DNS also known as Domain Name System is Regterschot's website. Where a user can view data.
User BrowserBrowser that's used by a user to access the website.
CDNContent Delivery Network is a service that distrubutes user requests to increase performance.
Load BalancerLoad balancer is a REST-API. It's used to distribute incoming traffic across virtual machines. 
Web app Webapp ServersThis is the web application that we are making as the group Smalltalk.
DatabaseThe database is used so that the web application can get data to produce graphs for the dashboards. 
View DashboardsTo view a dashboard is an end goal so that the user can see the relevant graphs.
ServicesServices are the dependencies that our web application uses.
Data WarehouseThe data warehouse is where the data is stored of every single race.
Cloud StorageCloud storage is where data that is saved on the cloud is stored.


Deployment Diagram

BrokerServerThe brokerserver will run with a brokerservice on it. This brokerservice will allow us to create large data-streams. This will in turn allow us to create dynamic graphs on our webpage without having to consult a database twenty times a second. This brokerservice is connected via a broker connection to the Java application API.
DatabaseServerThe database will contain all data that is not required to be updated to show real-time data. This will thus include all sensor-data of past races, as well as all data required for logging in and creating race-views. The database system we use is MySQL, because of it's accessibility and relative ease to use. MySQL runs on a databaseServer, that is connected to the Java Application API with the use of a JDBC (Java Database Connectivity) Database Connection.
ApplicationServerThe ApplicationServer will contain the API itself. This API will use Jakarta EE and Wildfly 25.0, which allows us to run an API with ease in a web environment. Using the REST API, this Java Application will connect to a webserver and deploy its .war artifact there.
WebserverThe webserver is the link between user and API and is the part of our API that the user can interact with. This webserver could also be described as a simple website.
User PCThe user PC is the eventual device on which the API and webpage will be run. This is the user end of our application.