Architectural Overview
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. Where a user can view data. |
|---|---|
| User Browser | Browser that's used by a user to access the website. |
| CDN | Content Delivery Network is a service that distrubutes distributes user requests to increase performance. |
| Load Balancer | Load balancer is a REST-API . It's 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 used so that the web application can get data to produce graphs for the dashboardsthe place where we store our data. |
| View Dashboards | To view a dashboard is an end goal so that the user can see the relevant graphs. |
| Services | Services are the dependencies that our web application uses. |
| Data WarehouseBroker | The data warehouse is where the data is stored of every single race. |
| Cloud Storage | Cloud storage is where data that is saved on the cloud is stored. |
Deployment Diagram
...
| 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
...