Previous page
Next page
Axxon Datacenter is based on the principles of microservice architecture. The microservices used are divided into two main types:
- AxxonSoft products include all products and services, that AxxonSoft manufactures and supports, necessary to deploy Axxon Datacenter: Backend, JobRunner, Arpserver, Vsaasmanager, Uploader, Configsync, Deviceregistry, Dictionary, Supplier, Query, Write.
- Third-party infrastructure products used to create the necessary environment: Haproxy, Nginx, NATS, PostgreSQL, Redis, Minio, ClickHouse.
As a rule, company products are installed in their docker containers, and infrastructure products are installed directly in the OS without creating additional architectural layers. TCP, HTTP/HTTPS, GRPC, RTSP and other protocols are used to exchange data between microservices.
Below is a general diagram of microservices' interaction and a description of each of them. It shows, for example, AxxonCloud, AxxonData and Monitoring servers, as well as a cluster combining several Axxon One servers. Note that Axxon Datacenter is deployed each time to meet specific customer requirements and may not, for example, contain AxxonData server or interact directly with Axxon One bypassing the merging cluster.
The diagram of microservices' interaction
AxxonSoft products
| Microservice | Description |
|---|---|
AxxonCloud | |
| Backend | The main infrastructure process. It processes requests in AxxonCloud, for which it makes requests to other microservices |
| JobRunner | Responsible for sending email, sms and push notifications |
| Arpserver | Establishes HTTP connection for data exchange between AxxonCloud and the remote Axxon One server |
| Vsaasmanager | Interacts with the supervisor on Axxon One side, configured in the FailOver mode |
| Uploader | Responsible for storing binary data (faces, their previews, and video recordings). The data is stored in the Minio database (described below) |
| Configsync | Synchronizes Axxon One configurations with the AxxonCloud database |
| Deviceregistry | Registry that is necessary for interaction between the hardware and AxxonCloud |
AxxonData | |
| Backend | Infrastructure service. Connects all AxxonData microservices and controls authorization |
| Dictionary | Stores and provides the schema of data storage and localization |
| Supplier | Receives events from Axxon One in dataloader format |
| Query | Builds reports |
| Writer | Writes data into the database |
| Exporter | Generates reports in PDF and CSV formats |
| Scheduler | Sends reports according to a schedule |
Infrastructure products
| Microservice | Description |
|---|---|
| Haproxy | Initially, load balancer: redirects incoming requests to the less loaded server. In Axxon Datacenter, also redirects requests, but using a filter: separately redirects traffic between arpserver and arpagent, and separately redirects other traffic. This is necessary because traffic between arpserver and arpagent goes over TCP via a unique proprietary protocol created by AxxonSoft, encrypted via TLS |
| Nginx | Web-server. Receives and processes individual parts of each web request, improves performance by caching static and dynamic parts of pages |
| NATS | Messaging system. Allows microservices to exchange data |
| PostgreSQL | Database. Stores all data except binary: configurations, users, domains, etc. |
| Redis | NoSQL database in RAM. Works with key-value structures |
| Minio | Database of binary files. Stores photos of faces, their previews, and video recordings |
| ClickHouse | Analytical database for AxxonData |