How many popular products have you named and launched? Naming products is hard to meet both usability and marketing objectives. This has never been as big of a problem for me, as GCPs APIs for example. Those are the true evil. Product names I care little for.
aws api and param names are stupidly long CamelCased and not even consistent half the time like a leaky abstraction over their underlying implementation
You remember any example? I don't call API directly and usually use CLI/SDK/CDK that work a lot better than gcloud. I did see some inconsistencies between services (e.g. updating params for SQS and SNS) and that could definitely be improved. But honestly, comparing to GCP mess, AWS is ten times better.
Why it's weird to blame them for product names? Because their purpose slightly different. I can see where negativity comes from and understand, but product name is a lot less important as consistent API experience. AWS is the best among big players by far, hats off and well-done to their teams and leadership. I hope the others will finally learn and follow.
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
Thanks for the clarification hadn’t appreciated the difference. Also somewhat reiterates my point which is nice as well
Have you named any successful product?
Yes, named a product and sold over 100,000 units of them. Naming products is hard but not that hard.
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.
How many popular products have you named and launched? Naming products is hard to meet both usability and marketing objectives. This has never been as big of a problem for me, as GCPs APIs for example. Those are the true evil. Product names I care little for.
1 reply →
aws api and param names are stupidly long CamelCased and not even consistent half the time like a leaky abstraction over their underlying implementation
You remember any example? I don't call API directly and usually use CLI/SDK/CDK that work a lot better than gcloud. I did see some inconsistencies between services (e.g. updating params for SQS and SNS) and that could definitely be improved. But honestly, comparing to GCP mess, AWS is ten times better.
why is that?
Why it's weird to blame them for product names? Because their purpose slightly different. I can see where negativity comes from and understand, but product name is a lot less important as consistent API experience. AWS is the best among big players by far, hats off and well-done to their teams and leadership. I hope the others will finally learn and follow.
2 replies →