Dsquares Loyalty Platform
  • Overview
  • App Components
    • Application Components Diagrams
    • API Gateway
    • Users Service
    • Merchants Service
    • Pointing Service
    • Vouchers Service
    • Payment Service
    • Channels Service
    • Gamification
    • C-Cubed
  • Hosting and Network
    • High Level Infrastructure Design
    • Hardware Requirements
      • Cloud
      • Bare-Metal Installation
      • Kubernetes
    • High Availability & Disaster Recovery
    • Observability
    • On-Premise Components
      • Introduction
      • Most workload on Dsquares cloud
      • Most workload on customer's premise
      • Hybrid setup
    • KSA Based Partners Solution
  • Data Flow
    • Description
    • Sequence Diagrams
      • DSquares System
      • Data Warehouse
      • Gamification
      • C-Cubed
      • API Gateway
      • Pointing Service
      • Vouchers service
      • Payment Service
      • Channels Service
  • Integrations
    • Introduction
    • Data Pipelines
      • Messaging Queue
        • Dsquares Kafka Library
    • Rest APIs
      • Rewards
        • Get Deals
        • Subscribe to offer
        • Verify Coupon Number
        • Burn Voucher
        • Burn PreGenerated Coupon
      • Points
        • Reward
        • Refund
        • Redeem User
        • Cancel Points
        • Get Wallet Data
      • 🎮Gamification
        • GetChallengesInfoForUser
        • GetProgressChallengesInfoForUser
        • GetBadgeChallenges
        • GetChallengeHistoryForUser
        • GetDetailsById
        • GetBadgeDetailsById
        • GetChallengeCategories
        • AddAction
        • UpdateIsClaimed
      • InsightsGathering
        • Participations Insights
      • Errors
  • Security
    • ISO 27001
    • Authentication
Powered by GitBook
On this page

KSA Based Partners Solution

PreviousHybrid setupNextData Flow

Last updated 8 months ago

Google Could Platform offers a region in El Dammam in KSA, the region is called me-central2 and sold through CNTXT, GCP's exclusive reseller in the region.

Each zone is hosted in one or more clusters and Compute Engine independently maps zones to clusters for each organization.

As your provider in the Dammam region (me-central2) of Google Cloud Platform, ensuring your applications' uptime is our priority. Here's how we ensure disaster recovery:

  1. Spread Across Zones: We deploy your services across multiple zones (me-central2-a, me-central2-b, me-central2-c) within the Dammam region. This way, if one zone experiences issues, your services remain unaffected in others.

  2. Data Backup: We regularly back up your critical data to another region. In case of emergencies, your data is safe and can be quickly restored.

  3. Traffic Distribution: Our load balancers efficiently distribute incoming traffic across all your instances and zones. If one zone gets busy or faces problems, traffic is automatically routed to others.

  4. Monitoring and Alerts: We keep a constant watch on your infrastructure's health using monitoring tools. If anything goes wrong, we receive alerts immediately, allowing us to take prompt action.

  5. Regular Testing: We conduct regular tests of our disaster recovery procedures to ensure they work when needed.

With these measures in place, your applications stay resilient, even in the face of unexpected challenges in the Dammam region.

We can use an existing Kubernetes cluster if the customer have one setup or install a new one, to install a new cluster we recommend the following configuration for high availability.

That's it for GKE Cluster, as for the DB:

Make sure the cluster is Regional (HA) and select the me-central2 region (El Dammam region in KSA)

For the node pool configuration, we enable Autoscaler with a minimum of 1 node per region (3 total nodes) and a max of 3 nodes per region (9 in total)

For the nodes, our app workload require high memory to CPU ration so we recommend using e2-highmem-2 (2 vCPU, 1 core, 16 GB memory) nodes for the default node pool (used for DSquares apps) with 100 GB Balanced Persistent Disk.

In Cluster Security Tab, select enable workload identity (we use it to authenticate Kubernetes Service Accounts to GCP to give Kubernetes workloads access to google APIs ex: gcsfuse CSI addon)

In Cluster -> Features, make sure to check "Enable Cloud Storage FUSE CSI Driver" we use it as our RWX storage class CSI plugin

Make sure you select SQL Server 2019, production preset setup, and "me-central2 (Dammam)" Region finally, make sure in "Zonal Availability" you select "Multiple zones (Highly available)"

Page cover image