Google Cloud Datastore with and w/o Protocol Buffers

While searching for information about the Google Cloud Datastore, I stumbled upon two different official documentation branches that seem to have the same content in terms of concepts, but provide code samples based on two different APIs:

  1. Here examples are based on the Protocol Buffers API.
  2. Here the same content is provided with examples based on the standard Google App Engine SDK.

Seems like the same set of actions are supported by both the APIs, but I'm not able to figure out what are the substantial differences between the two. Why should I choose one instead of the other, and why Google is offering both?

Answers


The difference is where your application will run. Datastore started as an App Engine-only thing, with App Engine-specific APIs, and was later expanded to support access from other sources.

If you're deploying to Google App Engine, choose #2.

If you're deploying elsewhere, and want to use Google Cloud Datastore as your repository, choose #1.


Need Your Help

What template language does Tumblr use?

templates themes template-engine tumblr

Tumblr uses a very simple template language for it's themes:

Linking Rust with C: undefined reference to '__aeabi' functions

c gcc rust libc eabi

I'm working on a project using Rust on an embedded device, where I'm trying to write functions in Rust that can be called from C. I compile the project without the standard library, more or less