AWS announced the availability of a new version of its Aurora database called Amazon Aurora I/O-Optimized. The big news in this release is that it removes all I/O charges for database usage, a move that should reduce overall database costs for customers with heavy workloads and provide more predictability. to your invoices from the cloud database.
“With Aurora's new configuration, customers only pay for their DB instances and storage consumption with no I/O charges. Customers can now confidently predict the costs of their most I/O-intensive workloads, regardless of variability, helping to accelerate their decision to migrate more of their database jobs to AWS,” the company said in a statement. a statement.
And getting customers to migrate more workloads is the goal, of course. But with more companies looking to operate more efficiently in the cloud, a product like this could appeal to increasingly cost-conscious CIOs.
It's important to note that it's a higher-priced product than the standard Aurora database, according to Corey Quinn, chief cloud economist at The Duckbill Group, a consulting firm that helps customers lower their AWS bills. . “It's an alternative pricing model. They charge more for this model as a baseline fee, so it will come down to the specifics of a given workload as to whether it's a good idea to use it."
En a blog post Announcing the new version, AWS's Channy Yun acknowledged that it depends on the type of job. “Now you can confidently predict the costs of your most I/O-intensive workloads, with cost savings of up to 40 percent when your I/O spend exceeds 25 percent of your current baseline spend Aurora data. If you are using Reserved Instances, you will see even greater cost savings,” she wrote. As you can see, and as Quinn points out, the devil will definitely be in the details of the particular requirements of the jobs to be transferred to the cloud.
Ray Wang, founder and principal analyst at Constellation Research, said it's a win for clients with heavy workloads. “Normally, any time you read data that isn't cached and then write it back to your MySQL or Postgree data, you incur an I/O charge,” he said. “This is designed to lower their prices because they have found a more efficient way to handle this internally, and have passed the cost savings on to customers as we enter the AI age.”
This should be especially useful for customers with data-intensive processes, such as AI or seasonal e-commerce use cases. Customers can bring in new workflows or move between Aurora's standard database and the I/O-optimized version in the management console, depending on expected workloads, to help manage costs.
