by Mike Masnick
Wed, May 28th 2008 3:41pm
Wed, Dec 4th 2013 8:50am
Closes: 24 Dec 2013, 11:59PM PT
We've all seen the digital panic that ensues when a massive service like Gmail or Facebook goes down for even a small portion of users. Smaller versions of the same thing take place every day with services that are less widely adopted but just as important to the people who rely on them. It doesn't even take an outage to cause problems — frequent slowdowns and interruptions can quickly cause a massive productivity traffic jam. With the degree to which we live our lives and do our work online, service problems are much more than a minor inconvenience, and at the wrong moment can be a disaster.
So we want to know: how does this impact the way you use the web? Are you prepared for interruptions in the online apps and services you use most? Have you ever abandoned an app for spotty performance, or adopted one specifically for its reliability? We're looking for everything in the way of insights, anecdotes and ideas about performance issues online.
You can share your responses on the Insight Community. Remember, if you have a Techdirt account, then you're already a member and can head on over to the case page to submit your insights.
One best response chosen by New Relic and the Techdirt editorial team will receive a free one-year Watercooler subscription on Techdirt (regular price $50). The subscription includes access to the Crystal Ball and the Insider Chat, plus five monthly First Word/Last Word credits, and can be applied to your own Techdirt account or gifted to someone else.
The case will be open for four weeks, with the best response announced shortly afterwards. We look forward to your insights!
by Tom Lee
Thu, Apr 10th 2008 11:57am
from the harping-on-huddlechat dept
If you've heard of HuddleChat at all, you already know about its demise. Put together by a few Google engineers in their spare time, the web chat application was used to showcase Google's newly-announced App Engine offering. There was just one problem: it was nearly identical to 37Signals' Campfire, a well-known SaaS web chat application. 37Signals gave some petulant quotes to ReadWriteWeb about the situation, and shortly thereafter Google pulled the app down.
As Om Malik has pointed out, this is all a bit ridiculous. AJAX/Comet chat is a fairly simple feature to implement. If my fellow participants in the Web 2.0 economy are counting on earning their keep via a collective conspiracy to make our jobs look harder than they are, we're all in deep, deep trouble. There's additional potential irony here, too, given that 37Signals has been accused of ripping off others' work to create Campfire in the first place.
But while this incident may prove portentous to the long-term prospects of the 37Signals business plan, it's hard to see how it could mean anything for Google. Breathless declarations that "many in the developer community [will] view Google App Engine as a Xerox machine for copycat product developers" are downright laughable. Google's decision to kill HuddleChat makes good PR sense, but it's inconceivable that many cost-conscious, Python-friendly startups would give up on App Engine over this minor blog imbroglio. As in many other respects, Amazon Web Services will likely provide the relevant template for these issues, and so far AWS has wisely avoided getting dragged into policing its users' apps.
Of course there's a lot of speculation that App Engine will include a free offering, and for that reason it may attract more troublesome users than EC2 currently does. But even if Google finds itself obligated to fight more griefers, phishers and spammers than Amazon does, it seems certain that they won't waste their time arbitrating squabbles over who called dibs on which trivial featureset. Sadly, that will remain for the courts to decide.
by Mike Masnick
Tue, Apr 8th 2008 12:27am
from the took-'em-long-enough dept
So, now, finally, nearly four years later, Google has come to its senses and announced its entrance into the web platform space with its aptly named AppEngine offering. In many ways, it's similar to Amazon's offering (which is a good thing!), though much more integrated, which could prove to be either a problem or a benefit depending on what you want to do. Amazon allows for a much more a la carte setup, which could appeal to many, while you have to really embrace Google to enjoy the benefits of its setup. A big open question is pricing. A huge part of the appeal to Amazon's Web Services platform is that it's crazy cheap. You really have to be working it quite hard to build up any sort of significant charges. Google hasn't released info on pricing yet, offering AppEngine up for free to the first 10,000 developers (who appear to have snapped up all the open slots in less than two hours). That free service has some limitations: initially 500 MBs of storage and enough bandwidth to serve approximately 5 million pages per month. There's some suggestion that the final service will always be free up to that level, with charges starting if you go beyond that. If so, that could certainly appeal to people who just want to try some stuff out for free.
While this may seem like something that will only appeal to serious techheads, this could be a really big deal. A lot is going to depend on how well AppEngine really works, and how open it really turns out to be. However, if it really does provide another super cheap (or even free at low levels) full service, highly scalable platform for all different kinds of applications, things could start to get very interesting pretty quickly. Between this and Amazon's Web Services, the very concept of developing online applications may finally start to change in significant ways for the better. The easier it is to develop and deploy highly scalable web applications, the more innovative and creative solutions we're going to start to see.