3 ms·
Much the opposite. GCP's names are painfully transparent and banal. No need to look them up, you can tell what they do from their names (which are proper nouns,
by twistedpair 5y ago
Much the opposite. GCP's names are painfully transparent and banal. No need to look them up, you can tell what they do from their names (which are proper nouns, so it's clear they're a service name)
- Cloud Logging - stores logs
- Google Compute Engine - VMs, compute
- Cloud Monitoring - stores metrics, monitors stuff
- Cloud Storage - stores stuff
- Google Kubernetes Engine - runs Kubernetes clusters
- BigQuery - runs multi-billion row queries with ease
- Cloud Functions - FaaS run time
Now sure, Cloud Spanner is a DB, without DB in the name, so you'll have to read the docs for a few seconds, but let's compare that to Cognito (brains?), X-ray (medical imaging?), Kinesis (something to do with mitosis?).
- oblio 5y agoAs a more generic term, kinesis just means "movement"/"motion", in Greek,
- drewda 5y agoMy own frustration is not with the overall product line names. My frustration is when specific options of each product line are discussed in relation to each together in documentation. Take the example of "GKE Ingress for HTTP(S) Load Balancing." It's overly generic and doesn't tell you at a quick glance whether you are buying a specific managed load balancer or running something yourself, and whether you are using basic exits to the public internet or buying into a global network accelerator.