Cloud Spanner

Auto Added by WPeMatico

Google’s Cloud Spanner database adds new features and regions

Cloud Spanner, Google’s globally distributed relational database service, is getting a bit more distributed today with the launch of a new region and new ways to set up multi-region configurations. The service is also getting a new feature that gives developers deeper insights into their most resource-consuming queries.

With this update, Google is adding to the Cloud Spanner lineup Hong Kong (asia-east2), its newest data center location. With this, Cloud Spanner is now available in 14 out of 18 Google Cloud Platform (GCP) regions, including seven the company added this year alone. The plan is to bring Cloud Spanner to every new GCP region as they come online.

The other new region-related news is the launch of two new configurations for multi-region coverage. One, called eur3, focuses on the European Union, and is obviously meant for users there who mostly serve a local customer base. The other is called nam6 and focuses on North America, with coverage across both costs and the middle of the country, using data centers in Oregon, Los Angeles, South Carolina and Iowa. Previously, the service only offered a North American configuration with three regions and a global configuration with three data centers spread across North America, Europe and Asia.

While Cloud Spanner is obviously meant for global deployments, these new configurations are great for users who only need to serve certain markets.

As far as the new query features are concerned, Cloud Spanner is now making it easier for developers to view, inspect and debug queries. The idea here is to give developers better visibility into their most frequent and expensive queries (and maybe make them less expensive in the process).

In addition to the Cloud Spanner news, Google Cloud today announced that its Cloud Dataproc Hadoop and Spark service now supports the R language, in addition to Python 3.7 support on App Engine.

Powered by WPeMatico

Google Cloud expands its bet on managed database services

Google announced a number of updates to its cloud-based database services today. For the most part, we’re not talking about any groundbreaking new products here, but all of these updates address specific pain points that enterprises suffer when they move to the cloud.

As Google Director of Product Management Dominic Preuss told me ahead of today’s announcements, Google long saw itself as a thought leader in the database space. For the longest time, though, that thought leadership was all about things like the Bigtable paper and didn’t really manifest itself in the form of products. Projects like the globally distributed Cloud Spanner database are now allowing Google Cloud to put its stamp on this market.

Preuss also noted that many of Google’s enterprise users often start with lifting and shifting their existing workloads to the cloud. Once they have done that, though, they are also looking to launch new applications in the cloud — and at that point, they typically want managed services that free them from having to do the grunt work of managing their own infrastructure.

Today’s announcements mostly fit into this mold of offering enterprises the kind of managed database services they are asking for.

The first of these is the beta launch of Cloud Memorystore for Redis, a fully managed in-memory data store for users who need in-memory caching for capacity buffering and similar use cases.

Google is also launching a new feature for Cloud Bigtable, the company’s NoSQL database service for big data workloads. Bigtable now features regional replication (or at least it will, once this has rolled out to all users within the next week or so). The general idea here is to give enterprises that previously used Cassandra for their on-premises workloads an alternative in the Google Cloud portfolio, and these cross-zone replications increase the availability and durability of the data they store in the service.

With this update, Google is also making Cloud SQL for PostgreSQL generally available with a 99.95 percent SLA, and it’s adding commit timestamps to Cloud Spanner.

What’s next for Google’s database portfolio? Unsurprisingly, Preuss wouldn’t say, but he did note that the company wants to help enterprises move as many of their workloads to the cloud as they can — and for the most part, that means managed services.

Powered by WPeMatico

The new Dragon Ball game is powered by Google’s cloud

Bandai Namco Entertainment announced the latest entrant in its series of Dragon Ball games this week. Dragon Ball Legends is a player versus player (PvP) mobile game that has players from all over the world battle with each other in real time by using their move cards. From all I’ve seen, it looks like a pretty fun game, though I know nothing about Dragon Ball and I have an unreasonable disinterest in card-based games. What made me perk up, though, was when I heard that Bandai Namco opted to use Google’s Cloud Network to host all the infrastructure for the game and that one of the main components of this system is Cloud Spanner, Google’s globally distributed database.

To make a real-time game work at all is hard enough, but Bandai Namco wanted players from all over the world to be able to play against each other. There’s a reason most games distribute players into regions based on their geography, though. In a real-time game, latency matters, as every hardened PUBG player will tell you, and the farther you get away from the game server, the higher your latency will likely be.

As Bandai Namco’s Keigo Ikeda and Toshitaka Tachibana told me ahead of the launch, the team opted to divide every game second into 250ms intervals, so while the game looks like it’s real-time to users, it’s actually a really fast turn-based game at its core. “Technically speaking, to the user’s eye, it’s real-time, but on the server, players have their own turn,” said Tachibana. By opting for the Google Cloud Platform and Cloud Spanner as the database to keep track of all moves, the average latency the team has seen during its tests is 138ms, which allows for plenty of wiggle room.

To make all of this work, the team spent almost two and a half years building out the necessary infrastructure, and Tachibana admitted that the team learned quite a bit more than it expected about network latency. During early tests, the team wanted to create a peer-to-peer connection to have players battle each other, for example, but depending on the carriers, the difference in user experience varied too much. The team also had to learn how to best route traffic between players, something that most gaming developers don’t really have to think about most days. “We were pretty frustrated with everyone who wasn’t Google,” said Tachibana.

Indeed, Cloud Spanner is the core service here, and the team says it opted for it because it gives it a globally distributed strongly consistent database to work with. Because any change propagates across the global network within milliseconds, Cloud Spanner is actually a really interesting option for game developers who need low latencies and a ground truth that can be distributed between a global player base. Cloud Spanner is not a cheap service, and the team acknowledged as much, though, as Google Cloud Director of Solutions Miles Ward noted, providing the service isn’t cheap either. “Spanner does things from a consistency standpoint that you can’t get from anybody else, so it’s a place where we have to spend more, too,” he said (and before my friends at Microsoft email me: yes, Cosmos DB also offers features that are comparable to Cloud Spanner, as well as a wider range of consistency options).

The Bandai Namco team also noted that Google’s vast private network was another major factor behind its decision. Because Google owns its own network, the data can jump between fewer networks to reach both the central database and the opposing player.

To make Dragon Ball Legends run smoothly, the team is also using BigQuery to manage and analyze its data, as well as some of the company’s Firebase services.

Tachibana noted that Bandai Namco is placing a big bet on this new game, but that the team also wanted to create a benchmark for what a globally distributed PvP game can look like. “We hope that when other developers look to a similar gameplay, they’ll say that it’s hard to top,” he said. “And also, from a technical side, we know that the people who are part of the industry will understand how amazing it is to realize this entire process.”

If you are not a developer and just want to play a new PvP Dragon Ball game, I’m afraid you’ll have to wait a little bit longer, though. The game will arrive in Apple’s App Store and the Google Play Store later this year.


Powered by WPeMatico

Google Cloud Spanner update includes SLA that promises less than five minutes of downtime per year

 Cloud Spanner, Google’s globally distributed cloud database got an update today that includes multi-region support, meaning the database can be replicated across regions for lower latency and better performance. It also got an updated Service Level Agreement (SLA) that should please customers. The latter states Cloud Spanner databases will have 99.999% (five nines) availability, a level… Read More

Powered by WPeMatico