Database

There is one database and one structure for both the API and the App. However, some of the data utilized in the API or App is sourced from third-party APIs. Below are the sources, structure and all data-related information.

summary>Initial setup/summary>

To speed up development we have purchased the laravel/php backend with a SQL database, however, we would like to transition to noSQL, Node.JS or Dart and using micro services. Note: this is not a final decision, please share your thoughts and pros and cons. Currently our backend is calling data directly from the database without an api to hadle the requests.

Transition Phase One

To simplify development we will change the database to noSQL and connect the “Laravel Brain” with our temporary firestore setup. This new database will be accessible through an api In order to save time and keep the focus and resources on developing the prototype, we have opted to use Firebase (Cloud Firestore) as the database. While this is not the most cost-effective option, it is the most efficient for the moment. Part of this transition we will also separate the content database from the hudi database.

Transition Phase Two

At this point the new database and api should have fully replaced the old and therefore the old database should be removed

Permanent ideal solution

As soon as the resources are available and/or we start to increase traffic to Hudi we will then move our database over to GCP. There are many options that are more cost-effective and have greater capabilities, however, it will be time and resource-consuming as it would require us to develop our own infrastructure (e.g. firewalls, APIs, security measures, etc.).