<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Aurora on LeanerCloud</title><link>https://leanercloud.com/tags/aurora.html</link><description>Recent content in Aurora on LeanerCloud</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 20 Aug 2026 02:08:40 +0200</lastBuildDate><atom:link href="https://leanercloud.com/tags/aurora/index.xml" rel="self" type="application/rss+xml"/><item><title>Converting Aurora Serverless to provisioned for cost and performance</title><link>https://leanercloud.com/blog/2025-07-16-converting-aurora-serverless-to-provisioned-rds.html</link><pubDate>Wed, 16 Jul 2025 10:26:20 +0000</pubDate><guid>https://leanercloud.com/blog/2025-07-16-converting-aurora-serverless-to-provisioned-rds.html</guid><description>&lt;h2 id="serverless-is-a-scaling-tool-not-a-default"&gt;Serverless is a scaling tool, not a default&lt;/h2&gt;
&lt;p&gt;Aurora Serverless scales capacity up and down automatically, which is genuinely useful when your load is bursty or unpredictable. The trouble is that it gets adopted as a default for databases whose load is nothing like that, and at scale the per-capacity-unit price makes it an expensive way to run a steady workload.&lt;/p&gt;
&lt;p&gt;I think of Aurora Serverless less as a permanent home for a steady database and more as a temporary configuration that helps you discover the capacity a database actually needs, so you can then move it to a right-sized provisioned instance. If a database has been running at a roughly constant capacity for a year, it is not a Serverless workload.&lt;/p&gt;</description></item></channel></rss>