Knowledgebase

Google Technology: Everything That Matters, Briefly Print

  • googletechnology, google, troubleshooting, performance, diskspace, billing, guide, howto
  • 0

The whole category in one page.

ALMOST EVERYTHING IS SCOPED TO A PROJECT

Separate projects per application and environment, created under an organisation — one made under a personal account is lost with that person.

CONSUMPTION BILLING MEANS A DEFECT IS EXPENSIVE

Set budgets and alerts before building anything, and set hard quotas where they exist — budgets warn but do not prevent.

Clients calling services directly multiply any defect across every installation.

NEVER DISTRIBUTE LONG-LIVED CREDENTIALS

Use identities attached to the resource, and an organisation policy prohibiting service account key creation. And restrict every API key by origin and by which APIs it may call.

RULES AND AUTHORISATION ARE THE ONLY THING BETWEEN A USER AND YOUR DATA

Wherever clients talk directly to a service, deny by default, enforce ownership, and never let a client set a value it should not control.

WHAT MATTERS LOCALLY

On-device processing costs no data and works offline. Static maps instead of interactive ones. Fewer reads per screen. Every foreign-currency bill moves with the exchange rate.

MEASURE ON MODEST HARDWARE AND THROTTLED CONNECTIONS

Development machines conceal every performance and cost problem you have.

THE DATA IS THE PROBLEM, NOT THE MODEL

And establish whether machine learning is needed at all before building anything.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot