Amazon fails to address interoperability concerns; Flexiscale plans cloud platform

Just attended a session here at FOWA from Amazon’s Jeff Barr and Flexiscale’s Tony Lucas on cloud computing. These vendors have similar offerings (in kind, but not in scale; Flexiscale is tiny by comparison). Lucas had told me he would talk about interoperability between Amazon and Flexiscale but did not do so, nor did Barr mention it.

I took the opportunity to get in some questions at the informal gathering after the session. The context is that Amazon has had serious outages this year, which will not have gone unnoticed by organizations considering its platform; the ability to import and export AMI’s (Amazon Machine Instances) would help users to implement failover plans. Is either Amazon or Flexiscale considering support for the Open Virtual Machine Format (OVF), used by VMWare?

Neither is doing so. Lucas muttered something about standards driven by commercial agendas; Barr said Amazon would wait and see and did not want to standardise too early; and that customers were not asking for it.

What interested me was the intense interest from other developers who had come up to ask questions, in this topic of interoperability and avoiding lock-in. This makes me wary of Barr’s comment that there is little interest.

In mitigation, Lucas said that his company can already import AMIs, but does not do so because it might breach Amazon’s terms and conditions. Barr pointed out that AMIs are just Linux VMs so you can easily migrate their contents. Both good points. Nevertheless, it strikes me that VMWare’s vCloud offering goes beyond either Amazon or Flexiscale in this respect.

Lucas made a couple of other observations. He said that Google’s BigTable, which sits underneath the AppEngine API, is not open source and makes  it impossible to implement AppEngine on his platform. He added that Flexiscale was always conceived as a platform offering, not just on-demand virtual servers, and will announce a platform based on a 100% open source stack shortly (aside from the Windows version; sounds like there will both Linux and Windows available).

Sun’s Tim Bray declares end of Enterprise Software

In a dramatic session here at FOWA in London, Sun’s Tim Bray tore up his talk and spoke on life after the economic crash. While giving a near-apocalyptic prediction of tough times ahead, he said that certain technologies will be winners and losers. Winners: open source, agile development, web applications, cloud computing. Losers: enterprise software:

I do not see much future for enterprise software … you are not going to get any purchase orders

On the subject of cloud computing, he added that he is not sure what model is best – hosted applications, virtual servers on demand such as those from Amazon, or what. The main risk, he said, is lock-in.

Ironically his talk is being followed by one from Salesforce.com, where lock-in is real.

Clearly, and as Bray admitted, the ideas he is recommending are the same as what he would recommend anyway. That doesn’t make them wrong, of course. His dose of reality, despite his pessimism, won applause here.

There are a few more snippets from his talk on my twitter feed.

Future of Web Apps 2008 Day One: Web is DVD, desktop VHS

I’m at London’s dreary Excel centre for Carson’s Future of Web Apps conference, just before the opening of day two. Yesterday was a mixed bag; good when speakers talk technical; bad when they descend into marketing. The origins of the conference are as a start-up incubator; developers and entrepreneurs getting together to see what’s new and make contacts. It still has some of that flavour, but it has grown beyond that because web apps are a mainstream topic and Carson attracts generally excellent speakers. There is a good crowd here; I’m not sure if every last ticket sold, but it is pretty much packed out, though the dark economic mood is dampening spirits.

Digg’s Kevin Rose spoke briefly about his site’s new recommendation engine, which has been active since July or so. The idea is that Digg learns a user’s profile by examining clicks and votes, using it to customize what the user sees. He spoke about a forthcoming feature, where third-party sites will be able to call the Digg recommendation engine to get profile information that it can then use to customize its own site.

An interesting idea; though it raises several questions. How does it work – would logging out of Digg be sufficient to disable it? Will users opt-out or opt-in? How much of this kind of customization do we want anyway?

This whole theme of contextualization is a big one here; it ties in closely with social networking, and Google’s OpenSocial API is getting quite a bit of attention.

Blaine Cook (ex Twitter now Yahoo, Ruby guy and inventor of OAuth) gave a though-provoking session on scalability along with Joe Stump from Digg (and a PHP guy). They took the line that languages don’t matter – partly a reflection on Twitter’s scaling problems and whether it was Ruby’s fault. Other factors make language efficiency unimportant, they said, such as disk I/O and network speed; and the secret of scaling is multiple and redundant cheap boxes and apps which are segmented so that no one box  is a bottleneck. The case was overstated but the main points strike me as sound.

I’m wondering how many of the developers here are actually having to deal with these kinds of scalability problems. Many web apps get only light use; the problems for everyday developers are different.

I attended a session entitled "The future of Enterprise Web Apps" by Googler Kevin Marks. It turned out to be a plug for the OpenSocial API; not what I was expecting.

Francisco Tolmasky of 280slides.com evangelised his Objective-J and Cappucino JavaScript framework, based loosely on Apple’s Cocoa framework. Hmm, bit like SproutCore.

I give Tolmasky credit for the most striking analogy of the day. The Web is DVD is says, and the desktop VHS. Adobe’s AIR is a combo player. He is talking about transition and leaving us in no doubt about what he sees is the future of the desktop.

Best sessions of the day (that I attended) were Blaine Cook on Jabber and its XMPP protocol, and David Recordon from SixApart on the evolving Internet "open stack". In this he includes:

  • OpenID + hCard for identity
  • XRDS-Simple for discovery (http://is.gd/3M53)
  • OAuth for authentication
  • ATOM and POCO  ( or PorC) – Portable contacts)
  • OpenSocial

I put these two sessions together because they both addressed the "Web as platform" topic that is really the heart of why we are here. Spotting which APIs and protocols will win is tricky; but if consensus is reached on some or all of these, they will impact all web developers and bring new coherence to what we are doing.

I’ll be covering today on Twitter again – see here if you want to follow.