AWS Polly is an example of a service that is tied into others.
To do anything more than a demo, Polly requires S3. To get a notification of a completed TTS synthesis, you must use AWS SNS. To get logs you have to use their logging service.
I suspect the primitives, like these required ancillary services, are the ones not tied in to each other. But how could they? (AWS probably has found ways)
For my project using Polly, I didn’t care. It was kind of interesting to explore AWS some.
But I’d guess a lot of folks might not want cloud service primitives. They want cloud products.
If they must use primitives to enjoy cloud products, they should want flexibility at least to not be stuck with pricing and feature set on primitives if they don’t compete.
To do anything more than a demo, Polly requires S3. To get a notification of a completed TTS synthesis, you must use AWS SNS. To get logs you have to use their logging service.
I suspect the primitives, like these required ancillary services, are the ones not tied in to each other. But how could they? (AWS probably has found ways)
For my project using Polly, I didn’t care. It was kind of interesting to explore AWS some.
But I’d guess a lot of folks might not want cloud service primitives. They want cloud products.
If they must use primitives to enjoy cloud products, they should want flexibility at least to not be stuck with pricing and feature set on primitives if they don’t compete.