Airport arrival and departure app - Create a web app that is able to read from a database of your choice and display incoming and outgoing flights of a given airport. Below are the high-level requirements.
- The application should highlight delayed flights based on arrival/departure scheduled times and the current system time.
- Provide an admin view that allows for the insertion of new inbound and outbound flights.
Tech details
- The front end should be written in angular and extra points are given if the design is responsive.
- Create as a Spring Boot application
- Define a simple schema that allows for the listing of inbound and outbound flights. Include information you deem relevant. List any assumptions made etc
- Based off Toronto Pearson Airport (YYZ),
- Assuming 6 months of data retention
- Average 1,300 flights arrive or depart from Pearson each day, 1,300 flights each day/24 hours ≈ 54 flights/hour. Assuming arrivals & departures are equal. 1,300 flights x 6 months retention period x 30 days/month = 234,000 flights in 6 months, i.e, 117,000 arrivals and departures, respectively. 100 GB storage space on the database will suffice.
- Average 130,000 passengers fly via YYZ each day, 130,000 passengers each day/24 hours ≈ 5,416 passengers/hour. Assuming passengers & maybe 2 of thier loved ones visit the flight board app for updates during their arrival/departure windows, which makes 5,416 views/hour x 3 = 16,248 views/hour ≈ 270 views/minute ≈ 5 views/second visitor traffic. This translates to atleast 5+ read queries on the database per second. Hence the system has to be optimized for high reads compared to writes. This can be achieved with a cluster configuration wherein a primary DB receives writes and replica DBs for reads. DB indexes, DB server query cache, server-side caching, full-text search engine, etc... can help further to optimize performance.
- Assuming atleast twice the amount of requests, 5 views/second visitor traffic x 2 = 10 RPS with each task time of 100ms would require 1 core of compute power, 2 GB RAM per instance, Num. cores=RPS x Task time
- Admins work in 8 hour shifts and ONLY one admin makes updates to flight details at any given time, hence considering this workload insignificant.
- Peaks and troughs will require auto-scaling of the app & database.
- During epidemic events that would halt the airline industry, the services can be bought down to reduce costs.
- User traffic based on geography would require regional scaling
- Implementing solution in Microsoft Azure
- YYZs flight board currently requires users to refresh the page to load new or updated flight details. A better approach would be to push changes via a real-time messaging system
- Making a prototype based on YYZs flight board for arrivals & departures
- Using global airlines & airports data and massaging the data
Arrival feature component to display below tabular data. After admin logs in, admin features will be visible on the UI.
| Arriving time | Status | Origin | Airline | Flight |
|---|---|---|---|---|
| DELAYED | Dallas-Fort Worth, USA | AIR CANADA JAZZ | AC8974 |
| HTTP Method | URI | Description |
|---|---|---|
| GET | /arrival?from=:datetime&to=:datetime | Get flights between particular datetime intervals |
| POST | /arrival | Save new flight details |
| PATCH | /arrival/{id} | Update existing flight details |
Departure feature component to display below tabular data. After admin logs in, admin features will be visible on the UI.
| Departing time | Status | Destination | Airline | Flight # |
|---|---|---|---|---|
| DELAYED | Dallas-Fort Worth, USA | AIR CANADA JAZZ | AC8974 |
| HTTP Method | URI | Description |
|---|---|---|
| GET | /departure?from=:datetime&to=:datetime | Get flights between particular datetime intervals |
| POST | /departure | Save new flight details |
| PATCH | /departure/{id} | Update existing flight details |
| HTTP Method | URI | Description |
|---|---|---|
| GET | /airline?nameContains=:string | Get airlines based on user input |
| GET | /airport?nameContains=:string | Get airports based on user input |
| GET | /status | Get statuses |
Using Spring Data REST for backend APIs to speed up development
- Azure Database for MariaDB
- Azure Spring Apps
- Azure Content Delivery Network
- Azure Load Balancer
- Application Gateway
- Azure Web PubSub
This solution will cost CAD $1,300/month and upwards per region
- MariaDB
- Spring Boot
- Angular
- Bootstrap
- Fontawesome
- Limited verification scope to Google Chrome compatibility
- Github
- VSCode
