3 ms·

Aurora MySQL was released October 2014. https://aws.amazon.com/blogs/aws/highly-scalable-mysql-compat-rds-db-engine/ https://aws.amazon.com/blogs/aws/highly-sc

by ttfkam 3y ago

Aurora MySQL was released October 2014. https://aws.amazon.com/blogs/aws/highly-scalable-mysql-compat-rds-db-engine/ https://aws.amazon.com/blogs/aws/highly-scalable-mysql-compa... Aurora Postgres hit general availability October 2017. (Sorry, betas and early release offerings don't count.) https://aws.amazon.com/blogs/aws/now-available-amazon-aurora-with-postgresql-compatibility/ https://aws.amazon.com/blogs/aws/now-available-amazon-aurora... Quick math… carry the two… compute the partial differential equation… Looks like 3 YEARS between the release of Aurora MySQL and Aurora Postgres.

vasco 3y ago
Yes, if you choose other definitions for launch dates you can come up with many different timespans.
- ttfkam 3y ago
  You're right. I should use the GA announcement for Aurora MySQL as well. …which was November 2015. https://aws.amazon.com/blogs/aws/now-available-amazon-aurora/ https://aws.amazon.com/blogs/aws/now-available-amazon-aurora...
  - vasco 3y ago
    So now tell me, between 7-9 years have gone by since Aurora is a multi database product, what sense does it make to assume its mysql? That's like saying at your company people call AWS "S3" or "SQS" because that's how it started. I don't even know what point you're trying to make because unless the majority of the time was mysql only and then recently other databases would've been added, the anecdote would still not make sense.
    - ttfkam 3y ago
      https://news.ycombinator.com/item?id=37085062 https://news.ycombinator.com/item?id=37085062 The majority of the time, it was identified as "aurora" in CloudFormation templates. 5.6 hit EOL in February of THIS YEAR, aka 2023. https://aws.amazon.com/blogs/database/upgrade-amazon-aurora-mysql-compatible-edition-version-1-with-mysql-5-6-compatibility/ https://aws.amazon.com/blogs/database/upgrade-amazon-aurora-... So… that would make it the majority of time, wouldn't it? Why does this upset you so?
      - vasco 3y ago
        Someone disagreeing with you doesn't mean they are upset my friend. Have a good one because we're not going to agree.

by ttfkam 3y ago

vasco 3y ago

Yes, if you choose other definitions for launch dates you can come up with many different timespans.

ttfkam 3y ago
You're right. I should use the GA announcement for Aurora MySQL as well. …which was November 2015. https://aws.amazon.com/blogs/aws/now-available-amazon-aurora/ https://aws.amazon.com/blogs/aws/now-available-amazon-aurora...
- vasco 3y ago
  So now tell me, between 7-9 years have gone by since Aurora is a multi database product, what sense does it make to assume its mysql? That's like saying at your company people call AWS "S3" or "SQS" because that's how it started. I don't even know what point you're trying to make because unless the majority of the time was mysql only and then recently other databases would've been added, the anecdote would still not make sense.
  - ttfkam 3y ago
    https://news.ycombinator.com/item?id=37085062 https://news.ycombinator.com/item?id=37085062 The majority of the time, it was identified as "aurora" in CloudFormation templates. 5.6 hit EOL in February of THIS YEAR, aka 2023. https://aws.amazon.com/blogs/database/upgrade-amazon-aurora-mysql-compatible-edition-version-1-with-mysql-5-6-compatibility/ https://aws.amazon.com/blogs/database/upgrade-amazon-aurora-... So… that would make it the majority of time, wouldn't it? Why does this upset you so?
    - vasco 3y ago
      Someone disagreeing with you doesn't mean they are upset my friend. Have a good one because we're not going to agree.