Skip to content

Sequence Diagram

Sequence Diagram

This section presents an overview of the calls being made between all parts throughout the entire system. These diagrams help visualize the flow of communication and the sequence of operations.

Launcher Initialization

The following diagram illustrates the initialization process when a game is launched:

OASOAS (Operator Account System)Game ProviderGPASOperator PortalPlayerOASOAS (Operator Account System)Game ProviderGPASOperator PortalPlayerAccess gameLaunch game requestCreate session (POST /sessions)Session responseInitialize game with sessionGame initializedGame readyDisplay game

Communication Between Microservices

The following diagram shows the communication flow during gameplay:

OASOAS (Operator Account System)GPASGame UIPlayerOASOAS (Operator Account System)GPASGame UIPlayerIf player winsPlace betBet requestDebit request (POST /movements/debit)Debit responseBet confirmedShow bet resultCredit request (POST /movements/credit)Credit responseWin confirmedShow win and updated balance

Error Handling Flow

The following diagram illustrates the flow when an error occurs and a rollback is needed:

OASOAS (Operator Account System)GPASGame UIOASOAS (Operator Account System)GPASGame UIError occurs during game processingBet requestDebit request (POST /movements/debit)Debit responseRollback request (PATCH /movements/rollback)Rollback responseError with rollback notification

Session Closure

The following diagram shows the process when a game session is closed:

OASOAS (Operator Account System)GPASGame UIPlayerOASOAS (Operator Account System)GPASGame UIPlayerExit gameClose session requestClose session (PATCH /sessions/close)Session closed responseSession closed confirmation

These sequence diagrams provide a high-level overview of the communication flow. For detailed information about each API call, refer to the Methods to Implement section.