Alex Barnett blog : BungeeLabs

The Great Bungee Jump

alexbarnett — Thu, 28 Aug 2008 00:21:00 GMT

Well, the great Bungee Jump has come. Martin Plaehn, CEO of Bungee Labs has shared the news of the company the letting go of 15 regular employees and contractors. Unfortunately, I am among this set of affected Bungee Labs employees.

A Voyage of Discovery

As Martin explained in today's post, Bungee Labs has been on a voyage of discovery. There are many lessons for me and the company to take away from the whole experience of the last year or so, but the bottom line is that we were overly optimistic about what it takes to achieve the rate and scale of developer adoption - real traction - and therefore the development of killer apps by the developer community that would drive the platform and the business forward at the velocity that makes a VC-backed venture "interesting".

So where does Bungee Labs go from here? Well, I think Martin eluded to the key clue:

"Over the next several months, Bungee Labs will lay out the course for a business object solution framework for user configurable enterprise-class applications that demonstrate these principles"

It'll be very interesting to see how this manifests and the impetus it will provide to the platform's adoption.

No Regrets

No regrets, none at all. When I considered the opportunity of joining Bungee Labs (and by doing so leave a relatively safe harbor in order to do so) I knew of the risks involved. Bungee Labs' mission was - and still is - of the kind that aims to "change the world". To have been a member of the team tasked with realizing the company's hugely ambitious mission has been nothing short of an entirely worthwhile and educational pursuit.

In my mind at least, Bungee Labs has made its mark in the brave new world of cloud computing. It has opened the eyes to many in the industry about what might be and can be. It has made cloudy ideas and visions more concrete and helped to define the concepts a (Platform as a Service, or PaaS) and memes that are contributing to the next generation of cloud computing platforms.

I've learned a great deal in the past 16 months working closely with a very talented, smart and creative set of teammates. And although it is probably unfair to call out individuals - for it implies those not mentioned weren't of similar caliber (which is not the case) - I do want to thank Martin Plaehn, Bungee Labs' CEO in particular for his mentorship during my tenure at Bungee Labs' and from whom I've learned an enormous amount management and leadership. I'll also miss the inane banter with Ted in those podcasts we put together (and the "Shushee" lunches).

What Next?

And so...on to my next adventure. What will that be exactly? Frankly, I have no idea yet...but whatever it is, I need to know I'll be trying to change the world :-)

I'm open to ideas...so if you have some, please get in touch.

Join me at Web 2.0 Expo New York - Building in the Clouds: Scaling Web 2.0

alexbarnett — Fri, 08 Aug 2008 13:06:00 GMT

I'll be taking part in one of the Cloud computing panels at Web 2.0 Expo New York this September, details below. If you want to meet up, let me know.

Building in the Clouds: Scaling Web 2.0

Jason Hoffman (Joyent, Inc.), Alistair Croll (Bitcurrent), Alex Barnett, Dwight Merriman (10gen), Jinesh Varia (Amazon Web Services)

10:30am - 11:20am Thursday, 09/18/2008

Performance & Scaling
Location: 1A23 & 24

Cloud computing is self-serve outsourcing for web companies. Clouds give even the smallest startup access to world-class infrastructure that can grow as needed. And developers build apps faster because they start with the building blocks of online applications: authentication, storage, messaging, and the social graph.

But the range of Cloud offerings is daunting. From self-contained development tools to virtual “bare metal,” selecting the right layer of Cloud offerings fundamentally changes how you run your business, what tools you can use, and ultimately how much control you have over your future.

Join this panel of Cloud computing innovators for the silver linings—and dark sides—of the Cloud.

Project Management as SaaS, Programmable Wikis and more

alexbarnett — Fri, 25 Jul 2008 17:52:00 GMT

Two new interview podcasts to share (recorded by me and Ted) for the Bungee Line:

Nate Bowler, CTO of @Task

@task (or AtTask) is a Utah-based tech company providing a comprehensive, web-based project and portfolio-management package delivered in both a SaaS and on-premise model with a very rich web API set. We talked with Nate about the evolution of their web services design and @task's future product plans in light of the market opportunities presented by the availability of the increasing number of 3rd party programmable web services.

Steve Bjorg, Founder and CTO of MindTouch

Prior to founding MindTouch Steve worked in advanced strategies at Microsoft focusing on distributed systems and web services. We talked with Steve about the MindTouch platform, its rich set of web APIs and the implications of a programmable wiki. MindTouch goes beyond providing open source wiki collaboration and content management - it's delivering a leading edge application integration and development platform called MindTouch Deki. Michael Coté, an industry analyst with RedMonk (analyst firm) picked up on both the podcast interview and news of the latest release of MinTouch Deki.

(About The Bungee Line: The audio podcast for web developers, covering web API's, software development, and the creation of (extremely) interactive web applications.)

Open Source in a SaaS World

alexbarnett — Fri, 16 May 2008 03:01:00 GMT

About a year ago, I took part in a meeting where the question: "What does open source "mean" in a SaaS world?" came up in conversation.

A year later, that same question is becoming increasingly pertinent as the IT industry's move to Software-as-a-Service (SaaS) and cloud-based computing accelerates.

For Bungee Labs (I work there), where

we provide an entire platform-as-a-service (PaaS)
developers create, share and re-use code and deploy apps in the cloud
developers "consume" and program against third party web apis and will create their own

...the "meaning" of FOSS is central within these different contexts and has many possible answers with many non-trivial implications...Three dimensional chess as it were.

(pic source: Memory Alpha, the Star Trek wiki)

For this post, I want to share some of the considerations relating to # 1) above: the context of open sourcing Bungee Labs' own system (Bungee Connect). Last month we stated that:

"Bungee Labs is evaluating several Free and Open Source Software (FOSS) licenses for the software components that comprise the complete Bungee Connect system. However, the task of reviewing the various FOSS licenses, and then identifying which of them best aligns with the software components and subsystems created by Bungee Labs–as well as ensuring compatibility with third-party components upon which Bungee Connect relies–requires considerable review and source code preparation. And we want to do this right, with the community’s involvement."

Since and before that announcement, Ted Haeger (who runs the Bungee Connect Developer Network) has been discussing some of the issues at hand and some of the options we see before us with some very "FOSS savvy" communities at events such as Socal Linux Expo, LugRadio Live USA and LinuxFest Northwest and of course with Bungee Connect's own growing developer community.

Today there's an interesting conversation going on between Ted and Simon Wardley, ex-COO of Zimki / Fotago who resigned last year over the company's decision not to open source their platform (the video of his announcement at a OSCON 2007 talk he gave "Commoditisation of IT and What the Future Holds" makes for entertaining and informative viewing all of its own...Simon discusses open source in a SaaS context. Update: Simon let me know of this video which also includes the slides

Anyway, back to the thread:

Simon wrote a post this morning providing his thoughts on the some the FOSS options available to Bungee Labs
Ted wrote back responding to Simon sharing his point of view
Then Simon responded to Ted

All three posts (and more to come no doubt) make an informative and interesting read, but I want to highlight one of the key issues in discussion.

The SaaS Loophole

The issue goes back to the question: "What does open source "mean" in a SaaS world?" and specifically the licensing issues. I'm going to quote and edit from Ted's post somewhat liberally (Ted owes me a Sushi, so we're quits now :P ) and isolate an (if not "the") open source licensing issue in the context of SaaS (my emphasis):

"Personally, I think that GPLv3 is the wrong license for freeing any SaaS or PaaS offering. The Free Software Foundation has a better license for this purpose.

GPLv3 is inadequate because it does not mandate that modifications that others make be opened. Originally, GPLv3 was planned to close up the “SaaS Loophole” (a.k.a. the “ASP Loophole”) in GPLv2. However, as I understand it, several large companies pressured the FSF to remove the key clause that would have closed the loophole.

What is the loophole? It’s this: if you take free software and offer it as a hosted service, then you are not conveying the software, and are therefore not obligated to reciprocate your modifications to the original code. In the context of service providers, GPLv3 is effectively the same as the BSD license. Many companies, Google among them, live inside this loophole. (For now, Bungee Labs is also in that camp.) Some remain there deliberately. Others are in it simply as a matter of course…that is, where they are in their business development process."

So that's the "SaaS loophole". Where's the loophole now? Ted explains:

"Perhaps the argument could have been made in the age of GPLv2 that the SaaS Loophole was an oversight, but now that GPLv3 has the loophole by design, it’s really no longer a loophole. The latest version of the license supports the practice. (And just to be clear, I am not advocating this for Bungee Connect.)

...Say Bungee Labs opens Bungee Connect under GPLv3. Is there a danger that small companies could replicate our offering? I don’t think that’s the case. But could a well-funded company do the same, fork the code, and then fund an engineering team to outpace the original inventors?

...The Free Software Foundation also provides the GNU Affero General Public License version 3, or AGPLv3. AGPLv3 specifically closes the SaaS loophole. Instead of being triggered by conveying the software, AGPLv3 is triggered by accessing the service. This helps to reduce the risk that a company could not branch the code and then out-engineer the originators, as the vulture company would be obligated to share-alike terms with their derivations."

So, is the AGPLv3 the right license for Bungee Labs to pursue? Is it the right license for SaaS providers? Is it enough on its own? (back to Simon Wardley's point in his post). Each company has their own unique circumstances and they each need to think through the 3D chess game. We're still working it out at Bungee Labs.

For us at least, I think some of the potential answers are becoming clearer, and others not yet. But it is the kinds of discussions that Ted is having with Simon that are a critical part of Bungee Labs' decision making process around FOSS. It cannot be an insular process.

Bungee Connect news x3 to share with you this morning

alexbarnett — Wed, 23 Apr 2008 12:46:00 GMT

Three big pieces of Bungee Connect news to share with you this morning:

1. Bungee Grid now running on Amazon EC2 and accessible to Bungee Developers

Bungee-powered application hosting on Bungee Grid-EC2 using Amazon’s Elastic Computing Cloud (EC2) infrastructure is available today upon special request for deployed Bungee-powered applications. The Bungee Grid-EC2 option is in addition to Bungee Grid-US, Bungee Grid-Europe. As a live example of a Bungee-powered app running on Bungee Grid-EC2, we've now deployed WideLens.com on Bungee Grid-EC2. Pricing model and other details available here.

2. Announcing Bungee Application Server

This is sweet: Developers wanting to deploy Bungee-powered applications on their own servers will be able to download a complete single-server Bungee Grid as virtual software appliance called the “Bungee Application Server”. The Bungee Application Server uses VMware technology and operates as a single complete management and delivery server for Bungee-powered applications. The Bungee Application Server will be first made available in June 2008 to BCDN Early Adopter Program (EAP) members. General Availability for sustained commercial deployment is expected in Q4 2008. More details including pricing and licensing info here.

3. Community Source Code Licensing plans for Bungee Connect technologies

Bungee Labs will make the source code available to the Bungee Application Server and the Bungee Pulse Client under several software source code licenses.

Two of these software licenses are available as of today in ‘draft form’ to facilitate community feedback prior to formalization in June 2008. These draft licenses are:

We're also answering this question:

Q: Is Bungee Labs is considering Free and Open Source Software (FOSS) licenses for the software components that comprise the complete Bungee Connect system?

Great question. Answers here...

Btw, I'm at Web 2.0 Expo in San Francisco this week. Let me know if you want to hook up!

So what is this Platform as a Service thing?

alexbarnett — Tue, 08 Apr 2008 14:54:00 GMT

The "platform-as-a-service", or PaaS meme is getting more air play the last 24 hours as news of Google App Engine makes its way through the tech media and blogs. ReadWriteWeb has a good write up and Phil Wainewright's summation by declaring "Let the PaaS wars begin" I think fairly captures the mood and reaction to the news.

Exciting times ahead no doubt, and pretty cool that Bungee Labs is getting mentioned in a number of blogs reacting to the Google App Engine news an example of the new generation of companies emerging in the PaaS space.

So, what is Platform-as-a-service? And why is PaaS interesting? Last week I had the opportunity to talk to Dana Gardner and Phil Wainewright in this sponsored podcast - full transcript available here - all about PaaS. I've taken the liberty of copy and pasting a snippet of the conversation below that speaks directly to the whole notion and definition of PaaS.

"Gardner: Okay, we’ve established that the tide is turning to the Internet, that there are some great Web-based services available, that technologies are now bubbling up to allow for better and easier connectivity. And yet, there is still a need for the right platform and the right infrastructure to make this all mission-critical and enterprise-ready.

So let’s get into PaaS as a possible stepping stone that, in a sense, bridges the best of the Web-oriented architecture and the available SaaS and the APIs-world with what developers inside organizations -- be they ISVs, service providers, or enterprises -- need to make these approaches acceptable and within the acceptable risk parameters.

I noticed that Bungee Labs does not call this "Development-as-a-Service" or "Deployment-as-a-Service" or "Integration-as-a-Service" -- but "Platform" as a service. Alex, give us the primer. What does "Platform-as-a-Service" really mean?

Barnett: That’s what we are trying to define at Bungee Labs. PaaS is one of those terms that we’re going to be hearing more and more. And they are going to be different -- varying levels of definition and interpretation of what that means.

But what we’ve done is put a stake in the ground in this respect, and then saying that in order to really be a PaaS -- and not just any one of those single pieces that you’ve mentioned plus more individual pieces -- that you need to be able to provide the end-to-end services to really call it a "platform."

From the developer’s standpoint, which is the development cycle, this means the tools that they need to develop applications, to be able to then test those applications, to be able to connect to Web services and to combine them, and to have all those kinds of capabilities -- and to then deploy and to make those applications instantly available to the business users.

Literally, we mean a URL that is the end-point for the end-user. From that, they can start consuming the application.

So, PaaS means having an environment in which you deploy inherently and have built-in scalability, reliability, and security. Once you’ve deployed your application, you know that you don't have to take care of all the infrastructure in the datacenter and the capital investments and the bodies that are required to make it scale when newer applications increases in use.

There is also the ability to connect to the various distributed data sources or functionality that the application needs to be able to consume. You can get that inside of that platform, the ability to be able to do that in a Web-native way, and so take advantage of the architectures we descried earlier, such as SOA.

There is also the ability -- and we touched on it earlier -- for developers to be able to collaborate on projects that are built-out in the cloud. They can share code, check in code, do all the standard revisions and collaborative-type functionality that developers need when they’re working on projects with teams distributed across the world or across your offices. And they can do this without having that entire infrastructure on-premise.

And then, the last, but critical, piece is having deep instrumentation and an analytics ability around the use of the application -- of how it’s being used, of where the connections are -- right across the board from the "glass of the window," the browser, for example, and right on through to the Web services in the CPU, or the rest of it.

As a result, you are able to understand performance. You are able to understand your billing, if it’s a billing proposition that you have. And all of what I described is comprised within six pillars [of Bungee's offerings]. All of that is delivered and available purely as a service, so there are no on-premises requirements for any of those components across the development and platform used in a utility model. You use it as much as you pay for, or as much as you use in a utility-based model -- all in the cloud. No bit needs to be installed on any machine at the enterprise in order to take advantage of all those Web services and functionalities.

Gardner: For our listeners who are just getting used to this concept of PaaS, let’s just get right in quickly and describe what Bungee Labs is. It’s a young, innovative company. And you’ve come out with a service called Bungee Connect. This is essentially one place online where you can go to develop, mash up, and access data, to put together Web-based applications and services, and then instantly -- with a click of a button, and perhaps I am oversimplifying -- develop and deploy in basically an integrated continuum. Is that correct?

Barnett: Yes, and provide very rich user experiences as part of that, with highly interactive application functionality. We’ve built out essentially that stack that I’ve described earlier. We've made that available for organizations to take advantage of. We're specifically targeted at developers who really want to be able to build very sophisticated Web applications that leverage orchestration workflow around connecting to Web services.

We are not in the business of being able to provide non-programmers with the ability to do these nice simple mashups.

Gardner: Well, if you can do that, let me know, because that would be a very good trick. I am sure the world would love to have development by anybody!

Barnett: Yeah, and that’s a great dream to be able to have, but inherent in that is inflexibility, because you are simplifying it all for the end-user. What we really offer is for the developers who are tasked with building sophisticated Web applications to do just that, deploy that, and then deliver very rich user experiences out on the Web.

Gardner: And to be clear, this is not just open source. This is commercial code, if they wish. The people who develop on this system, that code is their intellectual property. Is that right?

Barnett: The intellectual property of the code that is developed by the developers is absolutely their own intellectual property and remains so. We do have a community side of things that allows developers -- just as in the open source world -- to be able to share code and even entire applications as open source running on our grid.

But in terms of a company, it’s entirely their intellectual property that they developed and they are able to literally export the code. And if they want then re-factor that for a different kind of a grid or runtime, it’s their property.

Gardner: Phil, how do you see the relationship between PaaS and what Bungee Connect is doing, and then the larger SaaS trend? Do you see a relationship of one aiding and abetting the other? Or are they in separate orbits? How does that work out?

Wainewright: I think they are very much in a similar orbit. And to an extent, I don't think of PaaS as being part of SaaS or vice versa. It’s just everything moving to the cloud. These are two examples of that happening.

One of the things I want to highlight, as Alex was saying, is the useful experience. When people start developing for the Web, for the cloud, then it’s not just building the infrastructure -- it’s also learning what is involved in writing applications for that environment.

There is much more emphasis on the user experience. There is much more emphasis on reusing what other people have done, whether it’s by mash-ups or by reusing other people’s code, as opposed to reinventing the wheel every time. There is much more emphasis on developing applications and programs that can adapt and change to future opportunities in business conditions.

All of those things also have to be learned, at the same time as building the infrastructure. Using PaaS enables you to tap into that shared expertise in a way that you can’t do, if you try all by yourself.

The other thing that’s happening here is that we’re connecting into the resources of the Web, and getting onto the Web, so that we can interact with partners and customers and connect into those other Web resources. This is what we're really expected to do as businesses today, in order to stay competitive. So, there’s a tremendous pressure building to be able to do this kind of thing.

Now, there are three ways you can get onto the cloud. You can go to a cloud-computing provider and basically build your stuff in that cloud, which gets to some of the infrastructure, but, there's still the issue of how do I write applications in this environment and connect to other client resources.

Second, you can go to pure SaaS whereby you get a ready made application and you can do some customization, but there are going to be quite a few gaps around what that provides and what you actually want to do. There are going to be quite big gaps in terms of integrating that into your existing on-premises applications and to the other client application that you use.

Third, where PaaS comes in, it allows for the ability:

A) To get much faster to the custom applications that you need to build for that environment

B) To do the integrations to fill in the gaps and to access other SaaS applications and services, and to patch and connect back to the existing on-premises applications. "

Full transcript available here and podcast here. Bungee Labs' definition of Platform as a Service here.

See Results of Bungee Connect's Intern DevFest 2008

alexbarnett — Fri, 28 Mar 2008 12:54:00 GMT

In late 2007, fifty Computer Science university students applied for 2008 internships at Bungee Labs. We flew nine of the most promising applicants from around the US to join Bungee Labs for our first “Intern DevFest”.

Over a 24 hour period the students had to extend WideLens - the Bungee Connect calendaring reference application - to develop new features and create a new derivative WideLens application…then present the results to the judging panel.

The nine students slogged hard all day (with frisbee breaks!) and most of the night and then presented their mashup solutions to the judging team the next morning.

Check out the video highlights of the four winners.

Sync Google Calendar with Outlook and more with WideLens

alexbarnett — Thu, 06 Mar 2008 05:37:00 GMT

Google has just released a very cool utility (.exe download for Windows) providing users with the ability to synchronize their Google Calendar with Outlook.

Some nice features in their 0.9.3.0 release:

schedule the sync frequency: every x minutes
define directional flow: 2-way, and 1-way (either way)

A bit of a buzz going on about this...

Now, what if you could do the same over the web - no download, just use your browser (IE, FF, Safari)...? And not just Google Calendar <> Outlook, but others too...?

Well, it's certainly possible...First, watch this screencast I put together tonight (apologies for sound quality...done from home equipment):

About WideLens

A couple of weeks back Bungee Labs released a reference calendaring application, called WideLens, designed to show off some of the power of the Bungee Connect platform, from the kind of rich AJAX UI experiences delivered through to the high level of functionality developers can create by wiring up and integrating multiple web services and distributed web data sources into a single web app.

Video: WideLens User Experience
Video: Developer Overview

WideLens connects to Microsoft Exchange calendar, Google Calendar, Salesforce.com, Facebook, MySQL and iCalendar feeds, representing a variety of protocols and authentication schemes. MS Exchange is accessed through WebDav, Google Calendar through gData, Salesforce.com via SOAP, Facebook through REST and MySQL connectivity is based on client libraries provided by MySQL (integrated directly inside Bungee Connect).

WideLens is an uber-mashup.

WideLens connects to each of the sources in real-time, presenting the user with live data. With the exception of Facebook and iCalendar, users can create and modify events and those changes are immediately posted back to the source. MySQL pulls double duty, serving as both a WideLens native calendar source and as the persistence layer for all kinds of application data including user preferences and credential information for each service.

Developers: Have At it!

As mentioned above, WideLens has been released as a Bungee Connect reference application where we're encouraging Bungee Connect developers to customize the WideLens application as much as they want, deploy their own version of the app as their own app - to their own domain, at no charge, branded however they want and with whatever features / cuts / modifications / extended they want - the WideLens code is released under a BSD licence (read more here).

To get going with Bungee Connect and develop your own vision of what WideLens could do, sign up for your Bungee Connect account.

Time to Define "Platform as a Service" (or PaaS)

alexbarnett — Tue, 19 Feb 2008 09:27:00 GMT

Before joining Bungee Labs last year, I knew they were on to something big. I mean, really big.

A big idea, an ambitious vision: to provide developers with end-to-end development, testing, deployment and hosting of sophisticated web applications as a service delivered purely in the cloud.

Since we announced our private beta back in May 2007, we've had over 1,500 developers sign up. In January alone we had over 400 developers kicking the tires - not just signing up and disappearing, but 400 returning developers, learning, building and deploying out increasingly sophisticated apps on a fast evolving developer platform, requiring no install of anything on their machine - all through the browser.

And since May 2007, the trend to delivering software as a service (SaaS) has been moving at terrific pace. New web APIs are being made available every month and new announcements by start-ups as well established big players are reinforcing and fueling the acceleration to the inevitable world of cloud computing.

As we announce our move from private to public beta today, we've also tried to articulate the new category of product and service we believe Bungee Connect is at the forefront of defining, the category of Platform as a Service, or PaaS, and our big bet is that PaaS is the next big thing.

So what is a "Platform as a Service"?

In September 2006, Marc Andreessen posted his thought provoking "The three kinds of platforms you meet on the Internet" and it got a fair level attention from the web industry. And we took note. We thought what Marc was describing in his Level 3 definition where:

"A Level 3 platform's apps run inside the platform itself -- the platform provides the "runtime environment" within which the app's code runs.",

...was right, but only partly right. Given Bungee Labs' ambition and vision, we felt there was a lot more to Marc's definition of the highest level definition of an "internet platform", a definition more holistic and comprehensive than a runtime.

But we kept focused, kept working on what we were hearing our developers telling us we needed to fix and improve on Bungee Connect, to give what developers are telling us what they really want - a Platform as a Service - to provide everything required in the lifecycle for the development through hosting of full-on, sophisticated and highly interactive web apps, not just widgets.

As we were readying for our next phase -our public beta - we thought it would be a good time to put a stake in the ground and actually define what we mean when we use the term Platform-as-a-service, and thereby describe the comprehensiveness what Bungee Connect has to offer.

So early this morning, our CTO and Founder of Bungee Labs, Dave Mitchell posted a definition describing PaaS in concrete terms.

What follows is a summary of Dave's post, with a selection of my favorite "soundbites" and ideas, but I suggest you read the whole post for yourself - there's a fair amount to consider:

1) Develop, Test, Deploy, Host and Maintain on the Same Integrated Environment.

"It’s time to stop developing “here” and running “there”. Today, most applications are coded in one environment (usually custom-built for that project by a developer), then tested in another, and redeployed to yet another for production...In a completely-realized PaaS, the entire software lifecycle is supported on the same computing environment, dramatically reducing costs of development and maintenance, time-to-market and project risk. A PaaS should let developers spend their time creating great software, rather than building environments and wrestling with configurations just to make their applications run — let alone testing, tuning and debugging them...Also, an end-to-end PaaS should provide a high productivity Integrated Development Environment (IDE) running on the actual target delivery platform, so that debugging and test scenarios run in the same environment as production deployment.

2) User Experience Without Compromise

"A Platform-as-a-Service must deliver compelling user experiences, with all the richness and live interactivity that consumers have been conditioned to expect....Hiccups like software downloads or plug-in installations, browser dependencies and inconsistencies, or local executables break the web model, and are inherently less secure, less maintainable and less user-friendly. In order to be relevant and popular, PaaS must deliver the best user experience available on the web, comparable to or better than conventional approaches.

3) Built-in Scalability, Reliability, and Security

"Developers should be free to build applications with the comfort that the security of customer data, network traffic, source code (intellectual property) and even server hardware is maintained automatically by the platform through-out application development and delivery."

4) Built-in Integration with Web Services and Databases.

"Applications need to leverage existing software investments in databases, and internal or external third party web services, requiring that the platform offer a wide variety of connectivity options."

5) Support Collaboration

"A PaaS must support both formal and on-demand collaboration throughout the entire software lifecycle (development, testing, documentation and operations), while maintaining security of source code and associated intellectual property."

6) Deep Application Instrumentation

"With instrumentation, organizations can see exactly how users are using the application, the type of performance they are experiencing and any application crashes. This information can also be leveraged to create new business models where costs are tied to actual utilities, rather than flat-rate subscriptions or licenses."

Over the next couple of years we expect to be hearing a lot more about PaaS and how "Y announcement" by "X company" is now providing true a PaaS offering to businesses and developers.

But saying you are providing a Platform as a Service has to mean something, and we think the above definition sets a high but reasonable standard that must be met for any company to claim they are providing a "platform-as-a-service' and legitimately describe themselves as a PaaS player.

The amazing thing is, for me at least, is that Bungee Connect is delivering all of the above, today. From our point of view, delivering PaaS - the real deal - is not statement of Bungee's intent, it's a statement of fact. It's bold, but so is our vision. Yes, we've still a lot to do before we're commercially ready and we think that's coming soon, but so much is already there. Try it out.

Among the dynamos, My Data and advice for startups.

alexbarnett — Thu, 24 Jan 2008 14:41:00 GMT

SaaS / DaaS / WaaS (Whatever As a Service) and Mashups

Nick Carr quotes Henry Adams in Among the dynamos

“One lingered long among the dynamos,” he wrote, “for they were new, and they gave to history a new phase.

Pointing to SaaS Platforms trends, Clive Keyte write about "SaaS Management Platforms"

"Force.com is not on it’s own offering ‘cloud development facilities for SaaS applications though, there are a plethora of smaller companies entering into the fray including Bungee Connect"

Among the dynamos indeed...

And SaaS by the numbers: Salesforce.com: 24 Billion API Calls So Far

"This statistic along with others like 130 million transactions daily, 61,200 custom applications, and 750 AppExchange apps"

Bray Forrest informs us even Your Car Gets An API

"At the end of the month the Dash will get a RESTful API. At the user's initiative lat/long coordinates can be sent to a server. The Dash will consume a GeoRSS feed. This is just the first release. In the future they may add HTML pages, search and even the ability to poll. The device I saw did not have any API-driven apps loaded, but I can imagine great ones (update my location and finding out who from my YASN contacts are nearby)."

So what will we do with all these APIs? Mashups of course! What is a MashUp?

"Potatoes + beans + a little bit of beef + pork, and then you pour Smithwicks over the top of it."

Ah...Microsoft Research project alert: Rotunda: Profiling the Cloud

"the goal of the project is to be able to profile the performance of a Web application from the time a user clicks on a link and triggers an event in the browser—which triggers a database lookup—through each point of the resolution of the transaction."

Sounds a lot like Bungee Connect instrumentation designed to measure every transactions from user's browser interactions and server-side roundtrips, through to the app's service calls, triggers, events, response times, etc...You see, our business model demands we and our developers know this...we have this today :-)

My Data

The UK gets some relief from the ID Card madness, for a while anyway...turns out National ID cards scheme will delayed until 2012:

"The Government’s national identity card scheme was “in the intensive care ward” after leaked documents showed plans to issue UK citizens with the cards have been delayed until after the next election."

Phew! Seeing stories like this seems to be knocking sense to those who are living in cloud-cuckoo land...

On the other end of the "my data" equation: cries of "we want our data, when we want it and where we want it" are getting heard...

Here's video intro to DataPortability.org initiative: DataPortability - Connect, Control, Share, Remix.

"DataPortability gathers existing open standards into a blueprint for a social, open, remixable web where your online identity, media, contacts and content can follow you wherever you go."

Niall Kennedy's take on Data Portability, Authentication, and Authorization.

"Data authorization is the first step in data portability."

Enter OpenID and OAuth.

How will DataPortability.org keep from being hijacked by Microsoft? Now Microsoft has joined the fray, so does the inevitable questioning begin:

"So is the nascent DataPortability.org group at such risk from Redmond? Not according to a source inside the group."

News of Last.fm's on demand since CBS's acquisition hit the mainstream tech media yesterday. But what next? CBS Will Try To Convert Last.FM Acquisition To Video Value

“One of the reasons we liked the idea of buying it is, if we can develop a great social networking site around this music content, why couldn’t this extend in to entertainment, in to news sports, all businesses that we’re in"

Kaching!

Martin Plaehn's Quick Hits: Do's and Dont's of Entrepreneurship. 16 pieces of advice for start-ups.

"6. Do always accumulate choice; two by definition, three of four is better; then make decisions and have a back-up"

More Investments Into Open Source

News that Alfresco Gets Another $9M for Open Source Content Management

"Alfresco Software, an open source content management alternative to software created for large companies, has received an additional $9 million in a third round of financing, led by SAP Ventures and existing investors Accel Partners and Mayfield Fund"

However, not all the shareholders are happy with the Alfresco deal...Matt Asay wrote in New open source venture funding and the importance of SAP Ventures and Intel Capital

"But since we didn't need the money (not even remotely) and I didn't want the dilution, it's not my favorite news of the day."

Amen to that.

Uh Oh...

Mobile phone radiation wrecks your sleep

"Radiation from mobile phones delays and reduces sleep, and causes headaches and confusion, according to a new study, reports The Independent"

Podcast interviews - smart people in the world of the web

alexbarnett — Sun, 20 Jan 2008 15:41:00 GMT

One of the fun parts of my job at Bungee Labs is to partner up with Ted and interview some smart people in the world of the web. We publish these as a podcast series (the Bungee Line - podcast feed here) over on the BCDN blog.

If you have ideas about someone you think we should interview, let me know! We're focusing on topics we think web developers might be interested in the worlds of software as a service and web app development, in particular profiling web apis. Related topics are good too.

I've listed out below our most recent podcasts below...plenty more in the works (previous podcasts are listed here). Hope you like :-)

Alan Lewis on eBay Desktop and eBay APIs

"As product manager for eBay Desktop, Alan Lewis relies on the same web APIs that eBay makes available to all developers. In this edition of the Bungee Line, Alan tells us about what the eBay Desktop is, how it came about, and various details about eBay’s developer program and web APIs. We ask Alan about eBay’s position Oauth and on open source."

Toby Segaran on “Programming Collective Intelligence”

"Since the publication of his O’Reilly book Programming Collective Intelligence: Building Smart Web 2.0 Applications, Toby Segaran has become well noted for his ability to explain easily-understandable algorithms for the kind of deeply complex problems involved in social applications. Toby joins Alex and Ted to discuss some of the high-level concepts that he tackles in his book."

Jon Aizen of Dapper.net

"Jon Aizen joins Alex and Ted to explain how Dapper.net provides a no-fee tool for making almost any structured web site data accessible via a REST API. In a past life, Jon was involved in creating The Internet Archive. Jon also helps the Bungee Line introduce romantic intrigue into the podcast.

Punditry Alert! At the end of this show, Ted and Alex speculate a bit about Android, Google’s open source mobile device platform, the Apache License, and whether Robert Love is involved. Please consider this as another demonstration of Ted’s idiocy, brought to you by the Bungee Line."

Jeff Barr on Amazon Web Services (Part 2)

"In part 2 of our interview with Amazon Web Services evangelist Jeff Barr, Alex and Ted ask Jeff about Flexible Payment Service, virtual user group meetings in Second Life, the Startup Project, and pry at Jeff’s views of possible futures of technologies that developers might anticipate."

Jeff Barr on Amazon Web Services (Part 1)

"Developer evangelist for Amazon Web Services, Jeff Barr tells Alex and Ted about how he became a native Amazonian, his recent visit to “The Business of API’s Conference,” and a bunch of stuff on Amazon Web Services, including: Mechanical Turk, EC2, and S3. Additionally, Jeff explains the newly announced S3 Service Level Agreement*."

8 Trends in Software as a Service Platforms

alexbarnett — Sun, 13 Jan 2008 17:40:00 GMT

To kick off the new year, I presented to around 40 or 50 members of Utah Technology Council (UTC) last week. The title of the topic they asked me to speak about was "Trends in Software as a Service Platforms". I searched around for some ideas and came across two recent posts predicting trends in SaaS for 2008, one by Phil Wainewright "Eight Reasons SaaS Will Surge in 2008" and Jeff Kaplan's post "Top Ten Reasons Why On-Demand Services in 2008". I decided to borrow liberally from these (thanks Phil and Jeff) and mash these two together (along with a couple of thoughts of my own) and present "8 Trends in Software as a Service Platforms" to an audience made up of CTOs and VPs of engineering and development for software companies in the Utah area.

In preparation for the presentation, my boss (Martin Plaehn) at Bungee Labs suggested I write up my presentation as notes blog them afterward, so here they are.

8 Trends in Software as a Service Platforms

SaaS is just part of the web mega-trend
Mainstream opinion says “Yes” to SaaS
Software vendors stampede into SaaS
All is being virtualized
Explosion of Web APIs
Economic factors favor SaaS
Enterprise and SMB IT embraces SaaS
SaaS platforms proliferate (PaaS)

1. SaaS is just part of the web mega-trend

Most of us have witnessed and many of us have been a part of the transformation in the way goods and services have been digitized, virtualized, delivered and consumed. Software, the data behind that software and the functionality that software provides is no different - software is subject to the very same transformational forces.

Just think about how even a class of product that is natively digital - such as software - has been transformed in the way it is delivered and consumed. For prosperity's sake, I've still got a few of those ZX81 software cassettes stashed away somewhere, gathering dust, looking ever more antiquated with each passing year. How will today's mode of software delivery and use look to us in a few years from now?

The web wants to connect things, and that's interesting. But connecting and interacting with "live" data, information and remote functionality make things more interesting.

At the fundamental level, the web connects things. It connects people to people, businesses to businesses, and people to businesses. Since the early 90's, the web has enabled the connection of so many things to so many other things at an ever accelerating rate, and yet we crave even more connectivity. But we increasingly also want the ability to interact with those things.

And it is the nature of these connected things that have changed since the early internet. The early web was good at connecting to static views of information and accessing limited and rigid functional services, very much a read-only mode. Then, as we learned a) the ability to read more dynamic-type information - at least regularly updated, and b) access richer remote functionality, we created whole new opportunities for ourselves. Next, we grew our ability read and write against dynamic, near real-time data and information and to program against remote functionality to create a new class of web applications leveraging those capabilities - and hence a new order of business and experiential opportunities have emerged. Some label this as "Web 2.0".

At its essence, it is the "liveness" of these real-time read-write data, information and functional sources available as "always on" services and the increasing ease to connect to, interact with - specifically change those resources available as live, programmable services that allows us to create new value out of those resources, opening up brand new market opportunities for businesses and the compelling, rich "live" end-user experiences of tomorrow.

2. Mainstream opinion says “Yes” to SaaS

Not surprisingly, Wall Street loves the the predictability of subscription services. It's good for cash flow, forecasting and business planning.

The venture firms also relish the opportunities that are opening up in a software as services-oriented economy. The ability to circumnavigate the incumbent software players with new disruptive technologies and propositions that are significantly easier to try and access for prospective customers compared to traditional software evaluation, along with usage and subscription-based business models verses the old licensing model makes investing in services-based software companies very compelling propositions from the venture firms' point of view. We should also see healthy M&A activity based on these similar opportunities in the coming year.

And then there's the trend for offshore / IT business process outsourcing. These providers will surely get in the game and make their plays through investments in and acquisitions of SaaS vendors that align well with their current core businesses.

Add to that the excitement we're reading about the SaaS space from the IT Analysts, journalists and bloggers, plus the new book by Nick Carr (author of “IT Doesn’t Matter”) - delivered by Amazon to me last week: “The Big Switch: Rewiring the World, from Edison to Google”. I think there's little doubt Carr's excellent analysis of the computing industry as an analogy to the electricity industry's shift to a utility model will be on business bestseller list for much of 2008. His messages resonates with corporate executives and end-users agree with him:

IT is a needless hassle,
it should be as easy as electricity and
be as reliable as a utility

3. Software vendors stampede into SaaS

The Big Software Players are following the early SaaS successes

CRM as a case in point. If you've been following the CRM software market, you'll know about the noises Oracle-Siebel, SAP and Microsoft started to make in the 2007 about what they are are lining up for the 2008 in terms of CRM as a service. Their efforts to emulate Salesforce.com's success delivering CRM as SaaS will be key strategic bets from the incumbents' point of view - and loud, price and functionally competitive propositions from the point of view of their existing and prospective customers.

CRM is just one of the multiple horizontal solution categories to transform from on-premise with traditional licensing model to a service-based delivery and subscription-based revenue model. ERP, supply chain, e-commerce, HR and many more...the horizontal solution list goes on. And then there are the vertical solution players...

Here's another data point to consider regarding the move by traditional software vendors to a SaaS model:

“15-20% of application ISVs have already either begun new skunk works initiatives or gained access to SaaS assets and development experience through M&A activity”
(Source: Key Trends in SaaS: 2008 and Beyond, Saugatuck Technology)

4. All is being virtualized

Virtualization is a technology trend.

Virtualization enables hardware as a service. The demand for virtual machines met by hypervisor software (VMWare, Xen, Hyper-V) and the success of Amazon's Elastic Compute Cloud (EC2) in the last couple of years point to a continuation of further virtualization of applications and hardware. Virtualization is accelerating the move from traditional on-premise software to services.

Virtualization is a business trend.

We continue to become a mobile workforce. The younger entrants into the workforce in service-oriented economies expect and want to be always connected. It's very hard work, if not impossible to get your traditional on-premise applications and centralized servers sitting behind a firewall to serve today's mobile workers. SaaS and managed services meet the needs square on.

5. The explosion of Web APIs is upon us

According to ProgrammableWeb.com, there are 559 commercial and public APIs available today, most of these are new and there are plenty more to come. How many will we see go live this year? And how many private web APIs are there and will be developed and consumed in the coming year?

Data from ProgrammableWeb.com

6. Economic factors favor SaaS

On-premise software requires upfront capital investments
To lower costs, many companies hold back on their capital investments to mitigate their risks, especially in recessions
Adopting on-demand services on a pay-as-you-go basis will be a perfect sourcing strategy for businesses seeking greater cost-controls and flexibility – the utility model

All well and good, but the real economic value of SaaS is that fact that it unleashes new value of previously isolated data silos and functionality.

7. Enterprise and SMB embraces SaaS

When it comes to IT, who doesn't like

Low-maintenance?
Low cost?
Low-resource profile?

IT and business folk like these things, and externally delivered SaaS applications deliver these benefits.

8. SaaS platforms proliferate (PaaS)

The more mainstream SaaS becomes the more the large vendors will be forced to offer effective platforms for ISVs, enterprises and SMBs.

If the move by the software vendors from traditional on-premise software to a services model is to be successful, they will need to provide programmable interfaces - not just end-user interfaces - to their services for their customers. Customers need and want the ability to access, intergrate and create new value out of live, programmable data, information and functionality living in the cloud. And in turn these same customers will want their custom-developed composite applications and integrated data available as programmable services - yet more APIs.

Customers want to unleash new value of previously isolated data silos and functionality through the development of their own applications programmed against those resources. And in turn these same customers will want their own custom-developed composite applications and newly integrated data available as end-user interfaces and as programmable services - yet more APIs. These customer needs will drive the software market to provide platforms to provide businesses and developers with with end-to-end:

programmable services and data integration
application development, testing and collaboration tools
deployment and scalable delivery

...all as a service with a utility model.

(hey...I needed to mentioned Bungee Connect just the once ;-).

2008 will mark a the proliferation of such offerings as "platforms as services" (or PaaS) through 2009, where then the consolidation will begin. Interesting SaaS and PaaS times ahead.

Update 2/20/2008: see "Time to Define "Platform as as Service" (PaaS)

The presentation seemed to go down pretty well and we had lots of interesting discussion throughtout. One of the topics we discussed was data security in a SaaS world. Don Kleinschnitz (VP, Development at Symantec) followed up with a mail linking to his blog covering Security 2.0 topics.

Again - thanks to Phil Wainewright and Jeff Kaplan for their post and to Martin for suggesting I blog this.

OAuth Podcast

alexbarnett — Sat, 03 Nov 2007 14:45:00 GMT

Chris Messina (aka FactoryJoe), Larry Halff (of Ma.gnolia) and Eran Hammer-Lahav accepted our invitation to join Ted and me and discuss OAuth in our latest Bungee Line podcast.

What is OAuth? From OAuth Getting Started - Part 1, here's the jist of it:

"OAuth allows you to share your private resources (photos, videos, contact list, bank accounts) stored on one site with another site without having to hand out your username and password.

...Users don’t care about protocols and standards – they care about better experience with enhanced privacy and security. This is exactly what OAuth sets to achieve. With web services on the rise, people expect their services to work together in order to accomplish something new. Instead of using a single site for all their online needs, users use one site for their photos, another for videos, another for email, and so on. No one site can do everything better. In order to enable this kind of integration, sites need to access the user resources from other sites, and those are many times protected (private family photos, work documents, bank records)."

Adam Kalsey, summarizes it well:

"OAuth aims to standardize the way in which different consumer systems share data. The goal is to allow a person to give an application access to do some things on your accounts at other sites, but not everything. It’s role-based authorization for APIs."

OAuth is a big idea, but is it a "solution looking for a problem to solve"? I don't think so. The problem for end users today is real, i.e. authorizing one service to access your data by another service for use by the first service, securely and with control. For developers wanting to develop apps and services that create value through the use of customer data stored on other services, there is no standardized means set of protocols to lean on. Instead, developers need to waste time learning a new way for their app to be authorized to do so for each service provider, having to jump through the various specific means and idiosyncrasies of each service.

The current way is broken - too many means to the same end, for end-users, for developers leveraging service APIs and for the service providers themselves wanting to extend their services through web APIs.

OAuth is getting the attention from a number of people and services such as Six Apart and others ("Digg, Jaiku, Flickr, Ma.gnolia, Plaxo, Pownce, Twitter, and hopefully Google, Yahoo, and others soon to follow") have committed to run with it. This is good news, but we need to get the word out there and help make developers' lives easier. So, go listen to first OAuth podcast and evangelize OAuth!

Topics covered:

Background on Chris, Larry, and Eran
What problem is OAuth trying to solve?
What is the current identity landscape - what are the alternatives, and why is OAuth a better way for all?
How does OAuth work, who should use it?
What's the development experience like?
What's the end-user experience like?
What's the relationship between OAuth and OpenID?
Where is OAuth today?
What will it take for OAuth to succeed?
Who's backing OAuth - adopters?

Podcast with Jeremy Zawodny of Yahoo! - Part 1

alexbarnett — Tue, 02 Oct 2007 02:47:00 GMT

The latest Bungee Line podcast is up - this time an interview with Jeremy Zawodny, an 8-year-veteran of Yahoo! and currently a member of the Yahoo Developer Network team.

Lots covered, so much so that we had to break up the interview into two parts, Part 1 and er, Part two.

In Part 1 we discussed:

Yahoo!'s Zimbra acquisition
the Yahoo! Mail Web Services APIs
Jeremy's take on the Business Week article discussing Yahoo! Openness
the fruits of Yahoo! Hack Days and the Internal Yahoo! Hack Days initiative
Yahoo! Geocoding API
Yahoo! User Interface (YUI) Library
Yahoo!'s AJAX API for Maps

Part 2, we talk about about some of the recent topics Jeremy's been covering on his blog...will let you you know when it's up - in a week or so.

Presenting at AJAXWorld, Santa Clara

alexbarnett — Sat, 22 Sep 2007 02:37:00 GMT

This coming Monday I'll be presenting at AJAXWorld in Santa Clara, 10:10 - 10:55am

One of the demos I'll be showing off and demonstrating how to build is and deploy this Flickr / Google Maps using Bungee Connect to program against their REST(ish) service APIs. I'll also demo a Microsoft Exchange plus Salesforce mashup (it's a pretty slick example of what you can do with AJAX + SOAP web services integration)...and one other very cool demo app that I can't discuss here, just yet - you will just have to be at my presentation see it (and hear it). :-)

If you're going, let's catch up!