This topic defines key terms for microservices, organized by module.
SOFARegistry
Chinese | English | Definition |
Service registry | SOFARegistry | An open source service registry product from Ant Group. It implements service discovery based on the publish-subscribe pattern. It is not limited to service discovery and can be used for other general publish-subscribe scenarios. |
Data | Data | In a service discovery scenario, this refers to the network address and other additional information of a service provider. In other scenarios, it can represent any information published to SOFARegistry. |
Unit | Zone | A key concept in a unitized architecture. In a service discovery scenario, a zone is a collection of publishers and subscribers. Specify a zone name when you publish or subscribe to a service. For more information, see Active Geo-redundancy Solutions. |
Publisher | Publisher | A node that publishes data to SOFARegistry. In a service discovery scenario, a service provider is a publisher of its network address and other additional information. |
Subscriber | Subscriber | A node that subscribes to data from SOFARegistry. In a service discovery scenario, a service consumer is a subscriber to the network address and other additional information of a service provider. |
Data ID | DataId | A string that identifies data. In a service discovery scenario, it is usually composed of information such as the service interface name, protocol, and version number. It serves as the service identity. |
Group ID | GroupId | A string used to classify data. It can serve as a namespace for the data ID. Services belong to the same service only if they have the same DataId, GroupId, and InstanceId. |
Instance ID | InstanceId | The instance ID. It can serve as a namespace for the data ID. Services belong to the same service only if they have the same DataId, GroupId, and InstanceId. |
Session server | SessionServer | A server role within SOFARegistry. It is responsible for establishing long-lived TCP connections with clients and handling data exchange. |
Data server | DataServer | A server role within SOFARegistry. It is responsible for data storage. |
Metadata server | MetaServer | A server role within SOFARegistry. It is based on the Raft protocol and is responsible for consistency coordination within the cluster. |
Data center | Data Center | A physical area with a degree of independence in location, power supply, and network. It is an important factor in high availability (HA) design. Generally, within the same data center, the network quality is high, network latency is low, and the probability of a simultaneous disaster is high. Between different data centers, the network quality is lower, network latency is higher, and the probability of a simultaneous disaster is low. |
SOFARPC
Chinese | English | Definition |
RPC | RPC | Remote Procedure Call (RPC). |
RPC service | RPC service | The implementation object of an interface provided by the server-side. |
RPC reference | RPC reference | A proxy object created by the client for an RPC service. |
Service ID | service ID | A unique identifier for a service. It is composed of the full interface path, version, group, and communication protocol. |
Service provider | service provider | An application that provides an RPC service. |
Service consumer | service consumer | An application that uses an RPC service. |
Service registry | Service Registry | An independent application cluster that stores and maintains a list of addresses for all online RPC applications. |
Service parameter | service parameters | Parameters of a service provider that can be dynamically modified, such as weight and status. |
Service discovery | Service Discovery | The process by which a service consumer obtains the network address of a service provider. |
Dynamic configuration
Chinese | English | Definition |
Configuration class | Configuration class | A plain Java object in a business application. After it is registered using the programming API of the dynamic configuration framework, it becomes a resource that can be dynamically managed. This is called a configuration class. A configuration class instance is uniquely identified by its domain, application, and class ID. |
Domain | domain | A namespace for a configuration class. The default value is Alipay. It can be modified using programming annotations. |
Application | application | The name of the application to which the configuration class belongs. |
Class ID | class ID | A string that represents the configuration class. It matches the ID field of the @DObject annotation in the application code. The full class name is typically used. |
Property | attribute | A private property of a configuration class object that has public getter and setter methods. A configuration class can have multiple attributes. Each attribute corresponds to a configuration item in the business. |
Property name | attribute name | A string that represents the attribute. It matches the name of the private property in the business code. |
DataId | DataId | A string that globally and uniquely identifies an attribute. It is formed by combining the domain, application, class ID, and attribute name according to specific rules. |
drm-client | drm-client | The client JAR package for the dynamic configuration framework. |
Service administration
Chinese | English | Definition |
Running mode | running mode | The way the throttling guardian client handles traffic throttling. It includes monitor mode and intercept mode. |
Block Mode | intercept mode | When a throttling rule is matched, the request is actually intercepted. |
Monitoring mode | monitor mode | When a throttling rule is matched, the request is not intercepted. Only a log record of the throttling event is printed. |
Post-throttling operation: No action | post-throttling operation: null process | No action is taken. The system returns directly. For an interface method, it returns null. For a web page, it returns an empty response and ends the current page access. |