Master Domain Center (mdc)
Description
Domain entity storage.
Provides other roles within the site with access to data for organizing processes. Some data is pre-calculated inside the role.
Has direct access to the relational DBs of all domains, regardless of which sites serve them. On startup, loads domain data from the corresponding DBs into the cache.
Each domain maintains a permanent connection to its DB. Within each connection, a primitive query is executed every 5 minutes as a connection check. If the connection is lost, its recovery is initiated; during the absence of a connection, data of static collections managed by the domain center is available for reading but not for modification. When PostgreSQL streaming replication is used, the permanent connection is made only to the master instance of the DB server. However, after a restart or activation of the domain center microservice instance, if the master DB server instance is inaccessible, it can load caches by temporarily connecting to the recovery instance of the DB server.
Split into microservices by domains. Data is automatically synchronized between sites serving the domain.
Made redundant in Active-Passive mode. Scaled by splitting the domain tree.
Code |
|
Operation mode |
|
Redundancy mode |
|
Site types |
|
Layer |
|
Placement |
|
State preservation and recovery on restart |
|
Application |
|
Own storage |
|
Limitations
-
Present in the initial configuration.
-
Must be located only on the master site. On other sites, the sdc role is used instead.
-
If the role is unavailable, the master site does not function. As a consequence, other system sites do not synchronize domain data with each other. This matters when a domain is served on several sites.
Parameters
| Name | Type | Default | Description |
|---|---|---|---|
|
|
required |
Name. May consist of Latin letters and digits and must start with a letter. |
|
|
required |
Role type. Possible values: |
|
|
empty |
Additional role options. Contains a JSON object or list. |
|
|
empty |
Role activity flag. When set to false, the role does not participate in validation and is not started. |
|
|
empty |
Limit on the number of CPU logical cores used. Default: 0 - unlimited. |
|
|
empty |
Default logging level set specifically for the role instance (microservice type). More |
|
|
|
Flag allowing parameter differences in roles of the same group. Default: false - not allowed. |
|
required |
Connection strings to the PostgreSQL server farm where domain databases are located (created and used) with the entity storage managed by the domain center, and their change history. Each connection string defined in the aliases section lists the following parameters separated by commas:
For example:
|
|
|
required |
Group number. |
|
|
required |
Order of the role instance within the group. |
|
|
empty |
List of domain names served by this group. |
|
|
300 |
Timer interval that initiates keepalive requests to the domain DB. |
|
|
4 |
Limit on the number of simultaneously loaded domains. |
|
|
|
global |
Takeover mode switch.
|
|
false |
Switch for validating different settings of MDC instances in one group. When set to 'true', the validator stops blocking different instance settings, which may lead to loss of integrity. |
|
|
|
Domain distribution group number. Instances with the same value share the domain subtree ( |
Configuration example
Configuration management is performed in an application available to master domain administrators. The application hides the full configuration content, but it is still available through the API.
The configuration contains a section describing all instances of all roles. Parameters are defined for each specific role instance.
{
"name": "mdc1",
"roletype": "mdc",
"dbconnstrings": [
"alias://pgdb_strings/b",
"alias://pgdb_strings/c"
],
"group": 11020,
"order": 2
}