G Sheets vs MySQL (and other CMS stuff)

[Russinating]

So I think I know the answer, but basically what are the major differences between running a website's database (<2000 visits a month) off G Sheet rather than MySQL? I'm guessing G Sheets is slower when dealing with large volumes?

The reason I ask is it'd be easier for our team to add and amend content via a G Sheet rather than a MySQL db.

I realise I should be using another CMS, probably, that adds that usability above MySQL. And despite being 'ok' in PHP and writing websites in Notepad++, I've never touched Drupal/Joomla and the like and always get a bit lost when I look into them.

Any advice appreciated.

 

[Russinating]

I don't believe there's a row limit, and certainly not one that would be hit by our website. The benefit is we're fully Drive integrated and even a new starter could add a new row to a sheet (as opposed to SQL).

I've already written another site that uses G Sheet API and it wasn't too bad (and now it's all written).

The site would only need read access, and the sheet would basically be a database of projects to display. That blog doesn't mention anything about speed though which is my main concern.

 

[Russinating]

Ta. And whilst I agree on the row limit, I very much doubt we'd ever, ever get to even 500. That would mean we've worked on 500 individual client projects, all of which are being displayed online which would never be the case.

It doesn't get similar usage no, as it's for a targeted campaign, but the speed seems fine. The above helps, so I think it's certainly worth me looking at.