Some technical backend curiosity

[HungryBus]

Hey,

Since I'm a programmer, I'm curious what does AirwaySim uses for backend? If it is not a commercial secret, of course. I thought firstly PostgreSQL for data storage, but now I'm thinking that MySQL was the option, since the backend written on PHP, according to the links. If it is PHP, I wonder how it is so fast, knowing that there should be a lot of data queried on each refresh 

Code Select Expand

heavy redis caching, maybe?

[Sami]

Actually using MariaDB as the database engine, but it's rather simple without any specific tricks for that variant, so any MySQL variant should work out of the box for the code. PHP 8.x is the code base. We have a dedicated web server and a database server only for AWS (plus a few other servers for other projects, e-mails, backups etc.). Static content is served via Amazon CDN network helping with the speed.

The new website, in the works, will utilize a better set of ready modules from various vendors (with modern package managers to help administration), and will switch to a single-page application architecture for the game pages, and will use template engines from Latte(PHP) and Handlebars(JS) with prebuilt modules for extra performance, but rest of the backend and content management is our fully own software (used in some other projects for aviation sector clients too) in a similar way this current website is too (it's a fully new, "v.2.0", rewrite of our own "CMS" with a strict adherence to MVC structure and application/module separation for cross-project usability for the same modules/code; it's also in use for an aviation operations control software).

[HungryBus]

Seems nice. MariaDB is actually a bit faster comparing to MySQL for replication & querying, so this might also add for speed. Really looking forward to see the mobile-friendly version as well

And respect for adhering to MVC structure