Google Cloud Game Backend and Analytics Solution | Mountkirk Games

Mountkirk Games Cloud Platform

Prev Question Next Question

Question

Mountkirk Games makes online, session-based, multiplayer games for the most popular mobile platforms.

They build all of their games using some server-side integration.

Historically, they have used cloud providers to lease physical servers.

Due to the unexpected popularity of some of their games, they have had problems scaling their global audience, application servers MySQL databases, and analytics tools.

Their current model is to write game statistics to files and send them through an ETL tool that loads theminto a centralized MySQL database for reporting.

Solution Concept - Mountkirk Games is building a new game, which they expect to be very popular.

They plan to deploy the game's backend on Google Compute Engine so they can capture streaming metrics run intensive analytics, and take advantage of its autoscaling server environment and integrate with a managed NoSQL database.

Business Requirements -Increase to a global footprintImprove uptime " downtime is loss of playersIncrease efficiency of the clous resources we useReduce lateny to all customers Technical Requirements - Requirements for Game Backend Platform 1

Dynamically scale up or down based on game activity 2

Connect to a managed NoSQL database service 3

Run customize Linux distro Requirements for Game Analytics Platform 1

Dynamically scale up or down based on game activity 2

Process incoming data on the fly directly from the game servers 3

Process data that arrives late because of slow mobile networks 4

Allow SQL queries to access at least 10 TB of historical data 5

Process files that are regularly uploaded by users' mobile devices 6

Use only fully managed services CEO Statement - Our last successful game did not scale well with our previous cloud provider, resulting in lower user adoption and affecting the game's reputation.

Our investors want more key performance indicators (KPIs) to evaluate the speed and stability of the game, as well as other metrics that provide deeper insight into usage patterns so we can adapt the game to target users.

CTO Statement - Our current technology stack cannot provide the scale we need, so we want to replace MySQL and move to an environment that provides autoscaling, low latency load balancing, and frees us up from managing physical servers.

CFO Statement - -> Services are deployed redundantly across multiple regions in the US and Europe -> Only frontend services are exposed on the public internet -> They can provide a single frontend IP for their fleet of services -> Deployment artifacts are immutable Which set of products should they use?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

C.

Based on the business and technical requirements provided, as well as the statements from the CEO, CTO, and CFO, the most appropriate set of products for Mountkirk Games to use would be option C: Google Kubernetes Registry, Google Kubernetes Engine, Google HTTP(S) Load Balancer.

Here is a more detailed explanation for why this option is the best fit:

Business Requirements:

  1. Increase global footprint: Google Kubernetes Engine (GKE) can be deployed in multiple regions to improve global coverage and availability.
  2. Improve uptime: GKE provides auto-scaling, self-healing, and automatic updates, all of which contribute to higher uptime and reliability.
  3. Increase efficiency of cloud resources: GKE provides a managed Kubernetes environment, which simplifies deployment and management of containers, and allows for efficient scaling and resource allocation.
  4. Reduce latency for all customers: Google HTTP(S) Load Balancer can be used to route traffic to the nearest GKE cluster, reducing latency for customers.

Technical Requirements:

  1. Dynamically scale up or down based on game activity: GKE provides auto-scaling based on CPU utilization or other metrics, allowing the game backend platform to scale up or down dynamically based on demand.
  2. Connect to a managed NoSQL database service: Google Kubernetes Registry can be used to store and manage container images of the NoSQL database service, and GKE can be configured to connect to the service.
  3. Run a customized Linux distro: GKE supports custom Linux images for containers, allowing Mountkirk Games to use a customized Linux distro for their game backend platform.
  4. Process incoming data on the fly directly from the game servers: GKE can be used to deploy containerized game servers, and Google Cloud Pub/Sub can be used to receive and process incoming data from these servers in real-time.
  5. Process data that arrives late because of slow mobile networks: GKE and Cloud Pub/Sub can be used to process data in near real-time, even if it arrives late due to network issues.
  6. Allow SQL queries to access at least 10 TB of historical data: GKE can be configured to connect to Google Cloud SQL, which can provide a managed MySQL database for storing and querying historical data.
  7. Process files that are regularly uploaded by users' mobile devices: GKE and Cloud Pub/Sub can be used to receive and process files uploaded by mobile devices.

CEO Statement:

  1. Last successful game did not scale well with previous cloud provider, resulting in lower user adoption and affecting the game's reputation: GKE's auto-scaling, self-healing, and high availability features can help ensure that the game scales well and has high user adoption and reputation.
  2. Investors want more KPIs to evaluate speed and stability of the game, as well as other metrics that provide deeper insight into usage patterns so we can adapt the game to target users: GKE and Cloud Pub/Sub can provide real-time metrics and analytics for monitoring and improving game performance.

CTO Statement:

  1. Current technology stack cannot provide the scale needed: GKE's auto-scaling and efficient resource allocation can provide the necessary scale.
  2. Replace MySQL and move to an environment that provides auto-scaling, low latency load balancing, and frees us up from managing physical servers: GKE and Cloud SQL can replace MySQL, and Google HTTP(S) Load Balancer can provide low latency load balancing.

CFO Statement:

  1. Services are deployed redundantly across multiple regions in the US and Europe: GKE can be deployed in multiple regions to provide redundancy and high availability.
  2. Only frontend services are exposed on the public internet: Google HTTP(S) Load Balancer can be used to expose the frontend services while keeping backend services private.
  3. They can provide a single frontend IP for their fleet

Prev Question Next Question