4 ms·

Wouldn't product launches like these be tied to usage data which AWS already has? Do specific customer requests change the development trajectory significantly

Wouldn't product launches like these be tied to usage data which AWS already has? Do specific customer requests change the development trajectory significantly?

freeone3000 6y ago
You can't have usage data for a feature that doesn't exist.
_msw_ 6y ago
From my perspective, we are fortunate to have a lot of customers and tons of feedback on what they want us to build for them. The most effective way for us to help deliver what customers want is to listen directly to their voluntary feedback. That helps us more deeply understand our customers through their individual stories and anecdotes, rather than looking at the averages that come from statistics and general surveys. For Amazon Aurora, there are a lot of additional features in development, including offering Graviton2-powered instances. I expect that will deliver price and performance benefits for customers, but it's not the only benefit that's in the works.
threeseed 6y ago
It depends on the AWS product. For the container systems e.g. ECS, EKS, Fargate they have an open roadmap where they drive much of the direction from the community: https://github.com/aws/containers-roadmap https://github.com/aws/containers-roadmap For others it's completely closed off. At my last company we spent tens of millions a year with AWS and they never listened to us. The account managers have zero pull.
marta_morena_28 6y ago
How would known usage data help you decide how urgently customers want to use a new feature that doesn't exist yet?
- notatoad 6y ago
  if amazon is prioritizing postgres/mysql development over aurora development because there's a lot more users using the regular postgres/mssql instead of the aurora equivalent, it's a bit of a reach to suggest that there'd be a lot more demand for aurora on a new processor type.

4 ms·

Wouldn't product launches like these be tied to usage data which AWS already has? Do specific customer requests change the development trajectory significantly

by actuator 6y ago

Wouldn't product launches like these be tied to usage data which AWS already has? Do specific customer requests change the development trajectory significantly?

freeone3000 6y ago
You can't have usage data for a feature that doesn't exist.
_msw_ 6y ago
From my perspective, we are fortunate to have a lot of customers and tons of feedback on what they want us to build for them. The most effective way for us to help deliver what customers want is to listen directly to their voluntary feedback. That helps us more deeply understand our customers through their individual stories and anecdotes, rather than looking at the averages that come from statistics and general surveys. For Amazon Aurora, there are a lot of additional features in development, including offering Graviton2-powered instances. I expect that will deliver price and performance benefits for customers, but it's not the only benefit that's in the works.
threeseed 6y ago
It depends on the AWS product. For the container systems e.g. ECS, EKS, Fargate they have an open roadmap where they drive much of the direction from the community: https://github.com/aws/containers-roadmap https://github.com/aws/containers-roadmap For others it's completely closed off. At my last company we spent tens of millions a year with AWS and they never listened to us. The account managers have zero pull.
marta_morena_28 6y ago
How would known usage data help you decide how urgently customers want to use a new feature that doesn't exist yet?
- notatoad 6y ago
  if amazon is prioritizing postgres/mysql development over aurora development because there's a lot more users using the regular postgres/mssql instead of the aurora equivalent, it's a bit of a reach to suggest that there'd be a lot more demand for aurora on a new processor type.