If you use GCE on LAMP, you're basically assigning yourself the sysadmin role. This is great if you want the most customizability out of your instance, but it's on you to take backups and ensure the database stays up-to-date with security patches and such. You can scale out MySQL however you wish.
If you go with Cloud SQL, we take the sysadmin role for you, but this means we can't let you flip various options to ensure you don't prevent us taking backups. We do all the database upgrades for you.
Before I worked at Google, I would generally use SQL providers versus running my own. If I decided I needed more control, I could always dump the database and self-host later. But the headache of self-hosting, particularly for small traffic sites, was always more painful than just getting an SQL instance from an IaaS provider.