Is that really cheaper than to just use a VPS for $5/month which offers compute and storage and everything?<p>The article says this about VPSs:<p><pre><code> You often end up paying for
resources even when you're
not using them.
</code></pre>
But how is that different with S3? They also do not store the data for free.<p>And you can delete a VPS via API just like you can delete an S3 container.
I use an approach with Github Actions where if I need small amounts of persistent data between runs, I use a filesystem based off a fresh branch in the same repository.<p>That branch is rebased down to $tip so it shares no commits, and the 'database' doesn't affect development in trunk.<p>Obviously this doesn't work for significant data analysis, but if it's just a question of 'what was the state at the last run' it's cheap and easy.
<p><pre><code> > Here's how to abuse GitHub Actions to run a database
> DISCLAIMER: DO NOT ABUSE GITHUB ACTIONS DO RUN A DATABASE!
</code></pre>
Meanwhile, a cloud VPS is down to €3.60/mo.<p>Provisioning a VPS takes ~30-60 seconds, and bootstrapping them with cloudinit is an option most places, so you could even spin them up and down as you need. But honestly, the effort isn't worth saving €3.60/mo. over.
The benefits include not having to pay for the cost of owning the machine and disk, the computing nodes are only spun up when needed, and when your task is completed, the computing resources are not billed, and your data is stored on the cheaper S3.<p>These are the benefits brought by Wesql, a new database based on S3 that is compatible with MySQL.