System Architecture

The ThrillPots system has 3 primary integration points:

At a high level, the diagram below provides a visual representation of the ThrillPots System Architecture:

image

Integration points

ThrillPots has 3 primary integration points. This section will discuss each integration point and explain the purpose for each.

Betting integration

When it comes to Jackpot contributions, unlike normal games, player's do not make direct bets to jackpots. Rather, bets (contributions) are made on behalf of players via the operator's backend system.

Let's imagine a hypothetical casino where the operator has deployed a sitewide jackpot which is available to all players and is active across all casino content available on the site. The jackpot will receive a contribution bet each time a player makes a bet on any of the games on the site.

In order for these contributions to be made on behalf of the player, a simple event processor needs to be deployed that receives player game play / bet events and for each event makes a contribution request to the ThrillPots system.

In most platforms, this can be achieved by building a Kafka, RabbitMQ (or similar) event/stream processor which subscribes to the relevant topic/channel and makes REST API calls for each relevant event received. For platforms that do not have a message or event bus available, these events could be dispatched to the event processor via an alternative RPC mechanism such as REST, gRPC etc. This decision is all up to you, the integrating platform.

To learn more about this part of the integration, go to Event Stream Integration

Wallet Integration

When it comes to the wallet integration for ThrillPots, this integration is almost the same as any game provider integration. The wallet integration covers the following flows:

  • Player token authentication
  • Single Transactions (Debit & Credit)
  • Batch Credit transaction (Multi-player payouts)
  • Transaction cancellation

Integration is done against the ThrillGate service and can be performed in either direction (operator-to-provider or provider-to-operator).

To learn more about this part of the integration, go to Wallet Integration

Operator-to-Provider

If you decide to do an operator-to-provider integration, you will need to expose the endpoints required by the ThrillGate Standard Wallet Interface. All documentation can be found in the ThrillGate Standard Wallet Integration API documentation.

If you prefer for ThrillTech to integrate to your wallet API (provider-to-operator integration), you will need to provide the APIs and an integration environment for ThrillTech to develop the integration.

Frontend Integration

The ThrillConnect service is designed to support all frontend integrations. It exposes both a REST API (for end-user functionality like opt-in) as well as a WebSocket event stream for ad-hoc messaging and event broadcasts.

It is suggested to make use of the ThrillConnect JS API middleware layer which can easily be included in your site's code, freeing you up from the integration details and allowing you to focus on the visual and UX of the presentation layer.

To learn more about this part of the integration, go to Frontend Integration