migrate - Database migrations. CLI and Golang library.

•    Go

---

Database migrations written in Go. Use as CLI or import as library.

migration migrations database postgres cassandra sqlite mysql neo4j mongodb crate ql databases sql mariadb spanner google-cloud-spanner aws-s3 google-cloud-storage database-migration

migrate - Database migrations. CLI and Golang library.

•    Go

---

Database migrations written in Go. Use as CLI or import as library.

migration migrations database postgres cassandra sqlite mysql neo4j mongodb crate ql databases sql mariadb spanner google-cloud-spanner aws-s3 google-cloud-storage

spannerr - A Go client for the Google Cloud Spanner REST API

•    Go

---

A Go client for the Google Cloud Spanner REST API

spanner googlecloud

nodejs-spanner - Node

•    TypeScript

---

Node.js idiomatic client for Cloud Spanner. Cloud Spanner is a fully managed, mission-critical, relational database service that offers transactional consistency at global scale, schemas, SQL (ANSI 2011 with extensions), and automatic, synchronous replication for high availability.

nodejs database sql spanner google-apis-client google-api-client google-apis google-api google google-cloud-platform google-cloud cloud

pontem - Open source tools for Google Cloud Storage and Databases.

•    Java

---

While this is not an officially supported Google product, we encourage you to file issues for feature requests and bugs. pontem can be run in various modes. Consult the usage guide for relevant examples.

google cloud cloud-storage-solution cloud-storage-application cloud-storage gcp spanner

protoc-gen-persist - GRPC SQL and Spanner persistence layer

•    Go

---

An opinionated protoc plugin that will help generate boiler plate go code for GRPC micro services projects that need to interact with a SQL or Spanner database. The code generation is accomplished by providing a protobuf file with proper annotations, and then running the protoc cli tool with the --go_out option, and the --persist_out options set to the same directory. Starting with this version we changed the command line parameters. On the --plugin_out option you can add path=source_relative to make sure that all the generated files will be created on the current directory. The default behaviour (don't specify the path=source_relative) will generate the files in the same directory with the source files or in a directory computed from the (persist.pkg) or go_package option.

grpc protobuf sql spanner persistence-layer protoc-plugin