Google today added multi-region support to Cloud Spanner, meaning that the global database service announced in February is now actually a global service.

Cloud Spanner makes it easier for developers to build cloud applications by offering both transactional consistency of a SQL database and the scalability of a NoSQL database.

Until today, however, the managed database service only included single-region support. The new release extends Cloud Spanner’s transactions and synchronous replication across regions and continents. This means a consistent experience across regions, and it reduces latency by putting the data much closer to the end user.

It’s also really easy to use, the company claims. “With Cloud Spanner, you can create an instance in just a few clicks, and then scale it simply using the Google Console or programmatically,” wrote Deepti Srivastava, product manager of Cloud Spanner, in a blog post.

Customers are already migrating their production workloads to Cloud Spanner, according to the blog, which sites marketing automation provider Marketo as an example. Previously, the company had to migrate its data to a non-relational database stack when it needed to scale its platform. But this made it difficult to keep its transactional data ordered.

“It was essential for us to have order sequence in our app logic, and with Cloud Spanner it’s built in,” said Manoj Goyal, Marketo's chief product officer. “When we started looking at GCP, we quickly identified Cloud Spanner as the solution as it provided relational semantics and incredible scalability within a managed service.”

In another example, Evernote, a cross-platform app for creating and sharing notes, will soon migrate to a single Cloud Spanner instance to manage more than 8 billion pieces of its customers’ notes. This will allow it to replace over 750 MySQL instances, the blog says.

For its part, Google has used Spanner internally for years and says the database “powers apps that process billions of transactions per day across many Google services. In fact, it has become the default database internally for apps of all sizes.”