🦾ARCHITECTURE

The system architecture is divided into three layers:

• API Layer provides the RESTful and Websocket interface required by each business module.

• Service Layer provides a variety of micro-services based on the gRPC framework, Akka-based distributor processes, and various daemons for collecting data and synchronizing data.

• Data Layer includes Apache Ignite for solving high-frequency transaction scenarios, Redis for caching, PostgreSQL for persistent storage, MongoDB for storing logs, Kafka for message queuing, while the system stores virtual assets on the Solana public chain.

The following is a detailed description of each service module:

• Account service: Provides account-related interfaces, including registration login, KYC information entry, personal information editing and other functions.

• Address service: Based on the independent PostgreSQL database, it ensures that other modules in the business layer cannot directly obtain the private key, and provides services such as address generation, address binding, signing, and encryption.

• Chain service: Through the chain service, various smart contracts and public chain ports can be called through the interface.

• Game service: Provides the interface required for each game module of Texas Hold'em games.

• Schedule service: Provides scheduled tasks, delayed tasks, immediate execution tasks and other scheduled tasks, millisecond error.

• Wallet service: It is used to record the changes of funds in various business scenarios of users in the system, as well as the exchange and transfer of funds.

• Notify service: Used for event notification to distribute events to various modules.

• Mint service: Mint for tokens and NFT tokens.

• Risk service: Risk control service. Used for user behaviour analysis and risk control.

• Defi service: Provides Defi-related service interfaces.

• Statistics service: Provides various statistical interfaces.

• Log service: A log service used to record all game behaviour and capital changes.