It's Postgres under the hood. The key-value service itself is Go and we run it on GKE alongside some of our other services.

Yep, that's the idea. If you had a user with ID 1, one scheme to get all her info could be storing attributes in keys such as:

  user:1:name
  user:1:email
  user:1:city

Then a prefix search for "user:1:" would get you the relevant keys for that user.

But you could also go another way and drop a JSON-encoded object in a single key and work with it inside your app, since that might be the fastest way to get something off the ground!