Hey Sébastien.

Thanks for reading and your remark. It’s true under certain conditions. First of all, the Cloud SQL database must have a public IP. If not, there are many consequences.

Firstly, the developers can’t works from their workstation (or they can, but with an ugly set up, I wrote an article on that).
Secondly, you can’t use that shared instance across several projects (VPC peering and transitivity issues make that impossible), except if you use a shared VPC (a shared VPC for dev project seems weird, but why not)

Sadly, the recent companies I worked too often set org policy to prevent Cloud SQL public IP.

In addition, I don’t like to waste resource, and money. Honestly, the night, the weekend, having a database up and running is awful.
But, Yes, I can stop and start the instance, that’s true!! Did you try? between 10 and 15 minutes to stop and start? What’s the joke?

IMO, Cloud Run solution is absolutely not perfect, but offers many new advantages compare to Cloud SQL.