HubSpot/google-cloud-datastore

Name: google-cloud-datastore

Owner: HubSpot

Description: Google Cloud Datastore

Created: 2015-11-09 17:38:39.0

Updated: 2016-06-04 18:28:18.0

Pushed: 2017-09-22 18:17:04.0

Homepage: https://developers.google.com/datastore

Size: 207

Language: Java

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

Google Cloud Datastore

Google Cloud Datastore is a fully managed, schemaless, non-relational datastore accessible through Google APIs infrastructure. It provides a rich set of query capabilities, supports atomic transactions, and automatically scales up and down in response to load.

The API is deliberately low-level to map to the underlying Datastore RPC model and provide more flexibility to developers and higher level library implementers.

This repository contains the source code of samples and developer resources related to Google Cloud Datastore:

• Service and protocol buffers messages definition
• Python protocol buffers client library and samples
• Java protocol buffers Java client library and samples
• Node.js samples

Samples

JSON

• Node.js, todo.js
• Ruby, todos.rb
• [Add yours here]

Protobuf

• Python
• Java
• [Add yours here]

Client libraries

JSON

• Node.js:

install googleapis

• Ruby (google-api-client)

install google-api-client

• Ruby (ActiveDatastore)

install active_datastore

• Dart
• [Add yours here]

Protobuf

• Python (readthedocs):

install googledatastore

• Maven/Java (javadoc):

endency>
roupId>com.google.apis</groupId>
rtifactId>google-api-services-datastore-protobuf</artifactId>
ersion>v1beta2-rev1-3.0.2</version>
pendency>

• [Add yours here]

Documentation

• Getting Started
• JSON API reference
• Protocol Buffers API reference

Filing Issues

1. For production issues and support, see Google Cloud Platform Support packages.
2. For bugs or feature requests, please first look at existing issues.
3. When applicable, create a new report.
4. For bugs, detail the steps to reproduce the problem and the affected version number.
5. For feature requests, articulate the usecase you are trying solve and describe current workaround.
6. Make sure to annotate the issues with the appropriate labels.

Contributing changes

• See CONTRIB.md

Licensing

• See LICENSE