Architectural Overview

<Provide a high level overview of the architectural design, for instance by means of an architectural sketch. Make sure you show at least all sub-systems, and links to external systems. The sketch can be informal. The use of UML is not required.>

DNS

The DNS also known as Domain Name System is Regterschot's website. Where a user can view data.

User Browser

Browser that's used by a user to access the website.

Load Balancer

s

Deployment Diagram

BrokerServer

The 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.

DatabaseServer

The 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.

ApplicationServer

The 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.

Webserver

The 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 PC

The user PC is the eventual device on which the API and webpage will be run. This is the user end of our application.