Chapter 4. Product scheme

The «Incoplax» platform has its own build process, Continuous Integration (hereinafter CI). The result is a distribution. This is a software directory packaged either in a Docker container or in a zip archive, supplied with a deployment script.

On each cluster server, a Docker container is created containing all necessary modules and assets. On all cluster servers, the container contents are identical. The container is supervised by the operating system daemon. Inside the container, a core node runs, providing orchestration and supervision of microservices according to the configuration. Termination of any process is handled by the superior supervisor, up to the operating system daemons.

When the configuration changes, the set of microservices on a specific server and/or their parameters may change. The core node applies the changes. Platform updates can be performed automatically inside running containers by replacing modules and assets and then restarting the container. In special cases, a per-server update can be used by creating a new container.

Each container stores the latest current configuration on disk and loads from it. System microservices then connect to external storages and load from them. In particular, the current configuration can be updated after the responsible microservices are loaded from the DB.

Products, distributions, and the build process

Each product version is delivered as a distribution. This is a separate Docker image and an update archive produced by the build in the CI process of the «Incoplax» platform stack. The platform CI process performs modular and system testing of the platform and its base applications.

The distribution of a finished product contains a software directory with the libraries of the included applications, including the «Incoplax» platform itself, environment files (assets), and runtimes. The software directory is filled sequentially with the build results of all applications included in the delivery.

product_assets

Other assets or runtimes (for example, JRE) can be added to the Docker image created on the basis of a Docker image with a suitable platform version.

In special cases, the build process can be customized with a different set of applications and assets.

Domains, product layer, and subject areas

All data in the platform belongs to domains. Domain functionality can differ significantly. A product layer can be installed into each domain of the communication platform. The product layer enriches the communication platform and gives it an information part. The product layer is delivered with the distribution or separately. The product layer is versioned independently of the platform.

The product layer turns the platform into an information and communication platform.

In the information part of the platform, a basic data model is created:

  • Classes

  • Controls

  • Editors

  • User roles

  • Web applications

  • Server microservices

  • Scripts

  • Packages

A class is a typed data structure for which a collection, REST API, storage allocation, and JS/TS wrappers are generated automatically. A package is a set of entities of various types, including specific interrelated classes, applications, roles, and microservices. All these entities in a package represent a specific subject area and solve a specific information and communication task. For example, the callcenter package is an information and communication framework that provides functionality for mass typed call processing, corresponding reporting, and services in a specific domain.

The package extends domain functionality. New roles appear for users, and web applications of the subject area become available to holders of specific roles. For example, in a call center these are the call center operator, supervisor, call center administrator, and their corresponding applications: workstation, Reports, Settings, etc. Microservices, client and server, are used to serve complex processes. Server microservices are activated together with the package, bound to a specific domain, connect to the platform API, and interact with each other by creating and modifying various entities.

One of the essential principles of the product layer is real-time change tracking. Each application or microservice can subscribe to changes in specific collections or entities to receive an instant notification.

Packages are created, exported/imported, and activated/deactivated in the base application of the product layer (Builder). Packages are created in a low-code form.