3 ms·

Cool, Google created a cloud-native solution for people who want to create games for Google Stadia. You can buy into the ecosystem, built on top of Kubernetes -

by tmpz22 7y ago

Cool, Google created a cloud-native solution for people who want to create games for Google Stadia. You can buy into the ecosystem, built on top of Kubernetes - the system recommended for large scale projects and teams with hundreds of servers (but not more then ~5,000). An ecosystem most knowledgeable SREs will recommend your team not use unless you are able to do a relatively large amount of due diligence and have dedicated staff who are domain experts for kubernetes. For Google Stadia. Which is pivoting into really pushing for exclusive titles, and was the driving force for some studios removing their games from Geforce Now, because unlike Google Stadia Geforce Now allows you to bring your own games which you already own and avoid re-buying the same game twice. Google is trying to get a juicy bite of the games industry by building a walled garden around exclusive titles and proprietary cloud setups. Microsoft and Sony have used the same tactics (particularly exclusive titles). The chief argument is access, the idea that more people can now game who previously couldn't, but I don't buy it.

outworlder 7y ago
> An ecosystem most knowledgeable SREs will recommend your team not use unless you are able to do a relatively large amount of due diligence and have dedicated staff who are domain experts for kubernetes Who are those 'knowledgeable SREs' and what are they recommending instead? Docker Swarm? VMs? There is a place for those approaches, but people often underestimate the amount of work that is involved to bring large services into production, work that has been packaged and commoditized by K8s, by domain experts. Moreover, it allows people to speak the same language and easily share their solutions. Actual domain experts are required (today) if you want to bring databases and other stateful workloads to Kubernetes. But stateless? I'll run MicroK8s in a Raspberry Pi if I need to run containers. There is so much stuff that's taken care of by K8s that I can't'see why one wouldn't use it, unless they need to just run a single container somewhere. > and proprietary cloud setups. Proprietary? https://github.com/googleforgames/agones https://github.com/googleforgames/agones You don't have to run it on GKE, you know. You can manage it yourself. Which I'm not sure why you would do, since you are complaining about the lack of domain expertise.
manigandham 7y ago
This has nothing to do with Stadia. It's open-source software (Agones) designed to run any kind of game server (packaged as a Docker container) on top of Kubernetes with easier management around things like scaling, rolling updates, session management, metrics, lifecycle SDK, etc. Google Cloud is just offering a managed version of this on top of GKE. AWS and Azure offer similar platforms and even more products (like AWS Lumberyard game engine).

by tmpz22 7y ago

outworlder 7y ago

> An ecosystem most knowledgeable SREs will recommend your team not use unless you are able to do a relatively large amount of due diligence and have dedicated staff who are domain experts for kubernetes Who are those 'knowledgeable SREs' and what are they recommending instead? Docker Swarm? VMs? There is a place for those approaches, but people often underestimate the amount of work that is involved to bring large services into production, work that has been packaged and commoditized by K8s, by domain experts. Moreover, it allows people to speak the same language and easily share their solutions. Actual domain experts are required (today) if you want to bring databases and other stateful workloads to Kubernetes. But stateless? I'll run MicroK8s in a Raspberry Pi if I need to run containers. There is so much stuff that's taken care of by K8s that I can't'see why one wouldn't use it, unless they need to just run a single container somewhere. > and proprietary cloud setups. Proprietary? https://github.com/googleforgames/agones https://github.com/googleforgames/agones You don't have to run it on GKE, you know. You can manage it yourself. Which I'm not sure why you would do, since you are complaining about the lack of domain expertise.

manigandham 7y ago

This has nothing to do with Stadia. It's open-source software (Agones) designed to run any kind of game server (packaged as a Docker container) on top of Kubernetes with easier management around things like scaling, rolling updates, session management, metrics, lifecycle SDK, etc. Google Cloud is just offering a managed version of this on top of GKE. AWS and Azure offer similar platforms and even more products (like AWS Lumberyard game engine).