Skip to main content
Version: Next

Action Flow

Architecture

Table of contents

  1. General Flow Description

General Flow Description​

The backend of our application is composed of several services and technologies that manage two internal functions:

  • Data Manipulation
  • Data Persistence

The data is provided in the form of HTTP requests created by the frontend. These requests are then sent to our REST API which will perform the data processing and provide the response back to the frontend, the initial requester.

To persist and save the data, the API is connected to a main database (mysql), which is used for saving our data models. Additionally, we have a second database (mongodb), that contains unstructured information about our MECs. This DB is also used for saving these procedures, as they are added to the database.

For handling requests, we use Nginx as a reverse proxy. It communicates with users using HTTPS and then forwards the requests to the API.