Architecture - IU-Capstone-Project-2024/MoniDorm GitHub Wiki

The system architecture for the infrastructure of our project

Backend System Architecture

Version 1.0 (06.06.2024)

backend_architecture drawio

Version 2.0 (23.06.2024)

backend drawio (2)

API (REST Contract)

Version 1.0 (11.06.2024)

contract-1.0.json

To the proper usage, upload the file to the next resource: https://editor-next.swagger.io/

Version 1.1 (11.06.2024)

contract.json

To the proper usage, upload the file to the next resource: https://editor-next.swagger.io/

Version 1.2 (11.06.2024)

contract.json

To the proper usage, upload the file to the next resource: https://editor-next.swagger.io/

Version 1.3 (21.06.2024)

contract.json

To the proper usage, upload the file to the next resource: https://editor-next.swagger.io/

Version 1.4 (23.06.2024)

contract.json

To the proper usage, upload the file to the next resource: https://editor-next.swagger.io/

Version 2.0 (10.07.2024)

contract.json

To the proper usage, upload the file to the next resource: https://editor-next.swagger.io/

Version 2.1 (13.07.2024)

contract.json

To the proper usage, upload the file to the next resource: https://editor-next.swagger.io/

API (Telegram Bot Web-Server API Contract)

Version 1.0 (26.06.2024)

openapi3_0.json

To the proper usage, upload the file to the next resource: https://editor-next.swagger.io/

Telegram Bot FSA Schema

bot-dialogue-fsa

PostgreSQL Database Schema

image

image

Architecture of notification system (Deprecated since 23.06.2024)

Relevant properly to the Grafana for now. It seems, that admin panel will have the same flow

notification_system

API-SERVER --> telegram bot server:

Notify Request:

{[
  {
    "placement": "...",
    "category": "...",
    "failure_date": "...",
    "description": "..." (optional)
  },
  ...
]}