Comment by andreif
2 years ago
That's completely opposite to my experience. Do you have any examples of AWS naming that you think is "teenage boy trying to be cool"? I am genuinely curious.
2 years ago
That's completely opposite to my experience. Do you have any examples of AWS naming that you think is "teenage boy trying to be cool"? I am genuinely curious.
BigQuery - Athena
Pub/Sub - Kinesis
Cloud CDN - CloudFront
Cloud Domains - Route 53
...
Pub/sub is more like SNS or EventBridge Bus to me
Perfect list, also:
Google Cloud Run - Lambda
Sure I get the reference to the underlying algebraic representation of coding but come on, Lambda tells us nothing of what it does.
Products (not brands, products) should be named in a way that means something to the customer afaic.
> Perfect list, also:
> Google Cloud Run - Lambda
ECS is the AWS equivalent of Cloud Run. GCP Cloud Functions are the equivalent of AWS Lambda.
ECS / Cloud Run = managed container service that autoscales
Lambda / Cloud Functions = serverless functions as a service
1 reply →
Have you named any successful product?
1 reply →
I thought you meant API and parameters. Blaming them for product names is weird to me.
It's nice when things do what they say on the tin. That being said, it's hard to build a "brand" when you start out with a generic name.
2 replies →
aws api and param names are stupidly long CamelCased and not even consistent half the time like a leaky abstraction over their underlying implementation
1 reply →
why is that?
3 replies →