Mountkirk Games: Building Scalable Backend and Analytics Platform
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 - What should you do to isolate development environments from staging and production?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.D.
The CFO is asking about how to isolate development environments from staging and production. This means that they want to have separate environments for development, testing, staging, and production so that changes made in one environment do not affect the others. This is a common practice in software development and deployment to ensure that any changes are thoroughly tested before being released to production.
Option A, creating a project for development and test and another for staging and production, is a valid solution. This approach involves creating two separate projects, one for development and test, and another for staging and production. Each project will have its own set of resources, such as virtual machines, databases, and networking components. This will ensure that changes made in the development and test environment will not impact the staging and production environment, and vice versa. Additionally, this approach provides better security by isolating the different environments in separate projects.
Option B, creating a network for development and test and another for staging and production, is also a valid solution. This approach involves creating two separate networks, one for development and test, and another for staging and production. Each network will have its own set of subnets, routing tables, and firewall rules. This approach provides a higher degree of control over network traffic between the different environments and ensures that changes made in one environment do not affect the others.
Option C, creating one subnetwork for development and another for staging and production, is a less ideal solution as it does not provide the same level of isolation as the previous two options. This approach involves creating two subnetworks within a single network, one for development and test, and another for staging and production. While this approach can work, it is not recommended as it can lead to potential network issues and security risks.
Option D, creating one project for development, a second for staging, and a third for production, is not a recommended solution. This approach involves creating three separate projects, one for each environment. This approach can lead to higher costs as each project will have its own set of resources, and it can also make it more difficult to manage and monitor the different environments.
Overall, Option A, creating a project for development and test and another for staging and production, is the most recommended solution as it provides the highest level of isolation and security between the different environments. Option B, creating a network for development and test and another for staging and production, is also a valid solution and provides better control over network traffic.
