Advantages of ScriptDb over Fusion Tables
google-apps-script
Solution
Here are few points to justify "why use scriptDB"
- You do not have to use URLfetch to fetch data from Fusion Tables. Since you have relatively lower quota (as per my observation) for URLFetch
- ScriptDB is natively supported in App Script so it is faster and robust than your own implementation to access fusion tables.
- ScriptDB is key-value store (in the form of JSON) whose latency increases linearly as the DB size increases which is faster than all RDBMS whose latency increases exponentially with DB size. But I am not sure how Fusion Table behave as data size increases.
- ScripDB service has far higher quota than URLFetch.
- You can do maximum 5 queries in a second in fusion table but in scriptDB, there is no such declaration of query limit.
- size limit of ScriptDB: 50MB for consumer accounts, 100MB for Google Apps accounts, 200MB for Google Apps for Business/Education/Government accounts,. I think, this is sufficient for application developed using Apps Script.
You may check the FAQ section in below link for more detail. https://developers.google.com/apps-script/scriptdb
Problem
I have been looking through the new ScriptDb functionality - I am sure it is 'better' than Fusion Tables as a data store, I am just not sure how/why? Would anyone be able to suggest why it would be preferable (although not universally so, I am sure) over a Fusion Table?