I'm pretty disappointed with google sheet at the moment. I built some mildly complex spreadsheets for time tracking, nutrition, planning and such. They worked fine a year ago but I have experienced a massive drop in performance over the past few months. They take a minute to open and awfully slow to update calculations and no longer work reliably offline either. This is on an quad core desktop ffs.

This will kill cloud office apps if what works today doesn't work tomorrow. Cloud should not mean total loss of control of the version of the application. Something like gdocs should be offering frozen past versions of the app to avoid this type of thing being possible. Its not like frozen versions would actually add any maintenance cost to google.

These sheets are small and just have a few array forumulae. Nothing excel 20 years would have broken a sweat over.

If those server logs could contain customer-identifiable and/or confidential data, storing them in a cloud service might not be a good idea.

We kinda whipped up something for our own purposes (logging any data using google spreadsheets). It's called Sheetstorm and basically you just post data using the API and it'll automatically create a new sheet or append it to an existing one.

It's handy for logging and analyzing arbitrary stats.

https://www.sheetstorm.io/

This story reminded me of this:

http://www.pcpro.co.uk/news/80885/new-p2p-service-uses-gmail...

Note, it's from 2005, blast from the past.

To address the speed problem you could still leverage sqlite locally as cache layer in between your in-memory cache and longer-term google spreadsheet cache, and use a repeating job to move the sqlite data over to google spreadsheets (and subsequently delete those rows in the sqlite, keeping the sqlite db at a small size).