Lew Tucker bids Sun Cloud farewell
Lew Tucker, vice president and CTO of cloud computing at Sun Microsystems, spent his last official day at Sun Cloud on Twitter. The 115-character message was a succinct end to many years and many attempts by Sun to realize the commercial potential of scalable, on-demand, pay-as-you-go computing for the masses.
Sun Cloud (originally Sun Grid) was cheap and open to the public at $1.00-per-CPU hour way back in 2005, but it only ran a handful of high-performance computing (HPC) applications and demanded a high level of technical proficiency from users: They had to need and want the specific multitenant platform Sun had. Like grid computing, it had a small audience and never had the democratizing, ground-floor appeal of Amazon Web Services, which realized Sun's goals far more effectively than Sun had.
By 2008, however, Sun was cranking along with Lew Tucker, Java master and inventor (basically) of Salesforce.com's App Exchange in 2006. He seemed to be the man to carry out the plan and make Sun Grid into Sun Cloud, and Sun opened a fledgling storefront of cloud services that did rival Amazon's for capability -- but it was too late.
Oracle stepped in, bought the firm and put the kibosh on the cloud. Tucker's departure isn't a shock, but it's a firm signal that the Sun Cloud, arguably the first stab at an open-to-all public compute cloud service, is no more. Tucker is reportedly seeking a long vacation somewhere…sunny.
S3 adds a Recycle Bin
Amazon Web Services took another baby step on its road to being the Automat of on-demand computing with versioning for its Simple Storage Service (S3). Better known to the end user as the Recycle Bin, versioning means that S3 users everywhere can now recover accidentally deleted or modified files with a command. Before this, the only option for the errant data destruction was uncontrollable, vomit-inducing panic.
This kind of feature has been universally available in practically every online backup system for many years now, and most users have been making their own arrangements in regards to the dangers and utter lack of recourse in S3. AWS specialist Mitch Garnaat details how and why on his blog.