Aurora I/O optimized config saved 90% DB cost

Re:Aurora I/O optimized config saved 90% DB cost by vasco on Saturday August 12, 2023 @10:11AM (#37100378)

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

[ Parent | on HN ]

Re:Aurora I/O optimized config saved 90% DB cost by ttfkam on Saturday August 12, 2023 @10:44AM (#37100686)

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...

[ Parent | on HN ]

Re:Aurora I/O optimized config saved 90% DB cost by vasco on Saturday August 12, 2023 @12:49PM (#37102001)

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.

[ Parent | on HN ]

Re:Aurora I/O optimized config saved 90% DB cost by ttfkam on Saturday August 12, 2023 @10:50PM (#37106216)

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-...

So… that would make it the majority of time, wouldn't it? Why does this upset you so?

[ Parent | on HN ]

Re:Aurora I/O optimized config saved 90% DB cost by vasco on Sunday August 13, 2023 @01:52AM (#37107079)

Someone disagreeing with you doesn't mean they are upset my friend. Have a good one because we're not going to agree.

[ Parent | on HN ]