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.>
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 update
ApplicationServer
Webserver
This architectural overview is an overview that shows the building blocks of our project. It shows how we intend to build this project, besides that it helps the development team get a shared view.
figure 1: Architectural overview
Here you can see a description of what every building block of our project means. This makes the architectural overview better understandable.
| DNS | The DNS also known as Domain Name System is Regterschot's website. |
|---|---|
| User Browser | Browser that's used by a user to access the website. |
| CDN | Content Delivery Network is a service that distributes user requests to increase performance. |
| Load Balancer | Load balancer is a REST-API that is used to distribute incoming traffic across virtual machines. |
| Webapp Servers | This is the web application that we are making as the group Smalltalk. |
| Database | The database is the place where we store our data. |
| View Dashboards | To view a dashboard is an end goal so the user can see the relevant graphs. |
| Broker | The broker is used to receive live data from the sensors on the race car |
| Services | Services are the dependencies that our web application uses. |
table 2: glossary of architectural overview
...