Examinate Google Sheets as a Database Service for Web Applications

Hey guys,

I've examined using Google Sheets as a database service for webs and apps since it got popular with no-code. My examination focused more on the disadvantages, I have drawn some conclusion:

1. Google Sheets doesn't provide flexible search

Search is important for discoverability. It allows features like lookup by name, filter by a category, or specific criteria. Though, Google Sheets APIs don't provide any kind of search or query feature.

Except, Google Sheets allow adding invisible metadata ("developerMetadata"). Which limited to 30k characters for each sheet and each spreadsheet.

2. Quora and Storage limitation

Google Sheets allows storing up to 5M cells, and 18,278 columns to the entire spreadsheet. Each cell can't have more than 50k characters. For example, you build a movie discovery apps, it can store up to 600k - 800k video items. It can be a huge bottleneck for many scenarios

Besides, Google Sheet APIs start with 500 requests per 100 seconds. And it will charge based on requests

3. No proper schema and restriction

Google Sheets is like a database with its own presentation. For simplicity, it doesn't restrict its users on data schema. Which is the opposite of any database design.

Users can update the wrong type of content, rename the sheet tab or remove the entire sheet without any warning

The bright sight of Google Sheets is easy and free to get started, with great performance. With proper caching and tweaking, any apps with traffic < 5M visits/month can be safe with Google Sheets.

If those limitation isn't boring you, go ahead and use Google Sheet as a database service. Otherwise, best to choose using Google Sheet with the flexibility of moving out

Disclaimer: This is a shorter version of my recent post while examining using Google Sheets as a database service for inverr