-
Notifications
You must be signed in to change notification settings - Fork 598
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why did we go with the Protobuf API for Datastore rather than the REST/JSON API? #517
Comments
The reason is because JSON/REST has a much higher size overhead compared to Protobuf at the network layer and possibly other layers. Datastore is meant to be very fast and size efficient with potentially high throughout, so requests should be as small as possible. This allows a higher throughput of requests compared to using JSON. We use JSON for the other API requests because their payloads are potentially much larger, making the difference between a protobuf request and a JSON one negligible. |
Cool - thanks :) |
chore: relocate owl bot post processor
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
This PR was generated using Autosynth. 🌈 Synth log will be available here: https://source.cloud.google.com/results/invocations/b205fd33-200c-4298-88b8-18b0d1c79a3e/targets - [ ] To automatically regenerate this PR, check this box.
Just curious -- was there an issue with the REST/JSON API ?
The text was updated successfully, but these errors were encountered: