Ideas for project structure, data model, suggestions for interacting system components, e.t.c.

[nerosketch]

Идеи по концепции, модели данных, структуре проекта. Предложения по взаимодействию компонентов системы, и.т.д.

[F0rzend]

We decided to use English. Please change the issue

[igorek097]

in progress with data model...

[Ingco]

Abstract project architecture.

I propose this abstract project structure:

erDiagram
          TELEGRAM-API |o..o| Proxy : ""
          Proxy |o..|{ Client : ""
          Proxy |o--o| Backend : "external network"
          Proxy |o--o| TelegramBot : "external network"
          Backend }o--o| Postgresql : "internal network; self database"
          Backend }o--o| RabbitMQ : "internal network; AMQP, Message Queue"
          TelegramBot }o--o| Postgresql : "internal network; self database"
          TelegramBot }o--o| RabbitMQ : "internal network; AMQP"
          Dramatiq }o--o| RabbitMQ : "internal network; Message Queue"
          Dramatiq-periodic }o--o| RabbitMQ : "internal network; Static periodic tasks"

Loading

• Each rectangle represents a docker container.

• The ‘Backend’ and ‘TelegramBot’ connect to each other via RabbitMQ server (using AMQP). This allows us not to create a RestAPI for them, but to separate them into different containers.

• The ‘Backend’ and ‘TelegramBot’ use the same database container (‘Postgresql’) but can have different databases.

• The ‘Backend’ service can send background tasks (eg: newsletter) to the ‘Dramatic’ container.

• The ‘Dramatic-periodic’ will perform the recurrent payment tasks.