mike | Shared With: Everyone - Jul 08 2008 | google, docs, saas, reliability
I was also going to comment on the irony of a Google reputation survey, the same morning that Google Docs has been down for about 1 hour! People are twittering about it at the rate of about 2 tweets per minute:
http://summize.com/search?q=google+docs+down
But now back up after being down for 1 hour.
- mike | Shared With: Everyone - Jul 08 2008 | google, reliability, docs, saas
Google docs is down! This really sucks. I was happily editing in offline mode (using Gears), but didn't notice that the service was down until I tried to create a NEW document (which you can only do online!).
I turned off online access, and POOF, I can't see anything but the service unavailable page. AND, there is no way to GO BACK to editing offline again.
I just hope when it comes back, that I haven't lost my offline updates to docs I was working on.
- mike | Shared With: Everyone - Jul 08 2008 | pricing, adobe, acrobat, saas, pdf
Its interesting to me that Adobe is able to monetize PDF creation, when there are good free alternatives. Acrobat itself is too expensive ($300). I now see they are offering other price points for an online service for PDF creation:
- Free 5 trial (5 documents)
- $10/month
- $100/yearQuoted: Create Adobe PDF Online is the easy way to create professional-looking PDF documents. Offered by Adobe Systems, the inventors of the PDF file format.
Related Content from Around Faves
saas
-
1 FaverViewed: 2 TimesQuoted: It would take over 4 and a half years before the licensed software became cheaper. By that time, I'm quite sure there would be another solution that could replace SharePoint, and the cycle would start again. We can quibble about the numbers, but you get the point. Plus, the numbers don't reflect that the SaaS solution is likely to improve and innovate faster than the licensed software by a significant amount.
- mohit - May 11 20081 FaverViewed: 2 Times
- mike - Jul 08 20081 FaverViewed: 4 Times
reliability
-
We inadvertently provisioned a few database machines with MyISAM instead of InnoDB, and it has been a nightmare. I strongly advice against using MyISAM -- ever.
With MyISAM, we periodically get these incorrect "duplicate key" errors that don't go away until you run the lenghty "repair table" command that somehow fixes everything.
1 FaverViewed: 3 TimesQuoted: Use MyISAM when: The data isn't too critical ( "unreliable and slow, related to table size, table repair process" )
...
Use InnoDB for tables when: The table will be big (100Mb+ - "For reliability and performance, we use InnoDB for almost everything at Wikipedia - we just can't afford the downtime implied by MyISAM use and check table for 400GB of data when we get a crash." ) - mike - Aug 11 20081 FaverViewed: 1 Time
- mike - Apr 14 20073 FaversViewed: 6 Times
