RT @derek_downey
If you run apps on #GKE and want to use a #CloudSpanner database, this hands-on lab will guide you through the process using GKE Autopilot and Workload Identity so your apps can safely and securely connect to Spanner. https://lnkd.in/gU_rES7r

RT @derek_downey
For my game industry connections, check out this post on running (and scaling) your game infrastructure on Google Cloud using #GKE Autopilot. Don't miss that little, but critical (I'm biased), #CloudSpanner database. https://lnkd.in/gymMHMKT

A while back I chose to use #CloudSpanner on a (specific) project.

I documented the hell out of why, but not just why: I said why _not_ every other option on the table and a few that weren't because it illustrated how my team and I were thinking about the problem.

This lead to conversations. Some of them were also frustrating, but they ended up with a much better product.

Also when someone said "why aren't you using $foo" it was moderately gratifying to be able to say "see paragraph 3" :p

RT @derek_downey
Regional #compliance laws got you down for your #distributed #database?

#CloudSpanner now supports regional endpoints where data is stored and processed within the same region. https://lnkd.in/g4yQu_ZE

RT @derek_downey
Augmenting #relational databases with cache like #Redis is useful. But what if you need your data across regions, or even around the world? Checkout out how #CloudSpanner and Redis can help you achieve this scalability.

https://redis.com/blog/google-cloud-spanner-for-global-real-time-applications/

RT @derek_downey
I really like this #CloudSpanner migration overview. It covers all the main points (TEST TEST TEST!) and provides additional resources to deep-dive on where appropriate. https://lnkd.in/g4bbydbd

Okay this is another cool one: Now you can move your #CloudSpanner instance with zero downtime.

Application moved and need data to move? No problem! Expanding to global regions and need to shift from single to multi-region? No problem!

https://cloud.google.com/spanner/docs/move-instance

OOoooooh nice. #CloudSpanner implemented RETURNING (THEN RETURN is the actual directive in gSQL)!

I have to say, RETURNING is one of the reasons I <3 #Postgres more than #MySQL. Awesome to see it in Spanner.

The #CloudSpanner paper “Spanner: Google’s Globally-Distributed Database" received the 2022 SIGOPS Hall of Fame Award. While that in and of itself is pretty cool, what's more cool?

Hearing from Chris Taylor, one of the original authors of the paper, about the context and inspiration behind Spanner. ↓

https://cloud.google.com/blog/products/databases/reflecting-on-spanner-papers-sigops-hall-of-fame-award

#GoogleCloud

@garystafford scaled writes is a harder problem to solve of course. If the app has heavy writes as well I’d look to something like #CloudSpanner.

Does anyone know if #mastodon works with a more scalable #postgres compatible database like #gcp #CloudSpanner and similar? Just curious. That would probably be what I would do to scale a massive Mastodon instance dramatically.