Alex Barnett blog : PaaS

Platform Thinking

alexbarnett — Fri, 09 Dec 2011 15:41:00 GMT

(am republishing this blog post as it automagically disappeared in a server upgrade I did recently, originally posted 13.10.2011)

Last night I came across a rant from a Google employee (that was accidentally made public via Google+...doh!,) that provided not only good popcorn munching material, but I thought had some pretty interesting insights around what it really means to be a "Platform" company, not just a "Product" company.

It's pretty dense stuff, but wanted to call out the snippet about the "mandate" that Jeff Bezos sent around the company back in 2002.

So one day Jeff Bezos issued a mandate. He’s doing that all the time, of course, and people scramble like ants being pounded with a rubber mallet whenever it happens. But on one occasion — back around 2002 I think, plus or minus a year — he issued a mandate that was so out there, so huge and eye-bulgingly ponderous, that it made all of his other mandates look like unsolicited peer bonuses.

His Big Mandate went something along these lines:

1) All teams will henceforth expose their data and functionality through service interfaces.

2) Teams must communicate with each other through these interfaces.

3) There will be no other form of interprocess communication allowed: no direct linking, no direct reads of another team’s data store, no shared-memory model, no back-doors whatsoever. The only communication allowed is via service interface calls over the network.

4) It doesn’t matter what technology they use. HTTP, Corba, Pubsub, custom protocols — doesn’t matter. Bezos doesn’t care.

5) All service interfaces, without exception, must be designed from the ground up to be externalizable. That is to say, the team must plan and design to be able to expose the interface to developers in the outside world. No exceptions.

6) Anyone who doesn’t do this will be fired.

7) Thank you; have a nice day!

Ha, ha! You 150-odd ex-Amazon folks here will of course realize immediately that #7 was a little joke I threw in, because Bezos most definitely does not give a shit about your day.

then...

Over the next couple of years, Amazon transformed internally into a service-oriented architecture. They learned a tremendous amount while effecting this transformation. There was lots of existing documentation and lore about SOAs, but at Amazon’s vast scale it was about as useful as telling Indiana Jones to look both ways before crossing the street.

...Organizing into services taught teams not to trust each other in most of the same ways they’re not supposed to trust external developers.

This effort was still underway when I left to join Google in mid-2005, but it was pretty far advanced. From the time Bezos issued his edict through the time I left, Amazon had transformed culturally into a company that thinks about everything in a services-first fashion. It is now fundamental to how they approach all designs, including internal designs for stuff that might never see the light of day externally.

At this point they don’t even do it out of fear of being fired. I mean, they’re still afraid of that; it’s pretty much part of daily life there, working for the Dread Pirate Bezos and all. But they do services because they’ve come to understand that it’s the Right Thing. There are without question pros and cons to the SOA approach, and some of the cons are pretty long. But overall it’s the right thing because SOA-driven design enables Platforms.

Nowadays, it might be considered conventional wisdom for "Platform Thinking", but to truly embracing this philosophy - and make it real - first requires the realization that in the long term, Platform companies beat Product companies every time. Realizing that, then Platform Thinking and Platform Doing should become second nature. The brilliance of Bezos was to realize this strategic insight long before web APIs became as popular as they have become.

Federated Apps on the Intuit Partner Platform

alexbarnett — Wed, 03 Jun 2009 13:52:00 GMT

So what have I been working on since joining Intuit? A bunch of stuff, but something I wanted to shout about is the release of “Federated Applications” on the Intuit Partner Platform.

Working closely with five new developers to Intuit's Platform as a Service (PaaS), VerticalResponse, DimDim, Rypple, Setster, and ExpenseWare, we've got some kick-ass apps federated into the platform.

Some nice coverage so far this morning, including:

Ben Kepes, CloudAve Intuit Launches the IPP Version 2

"After the briefing I have to say that it looks to me like IPP is finally offering to fulfil the promise of the end-to-end integrated small business software platform that I’ve been evangelising for a few years now – my catch cry of late has been that application integration should only be seen as the very first step in building a SaaS ecosystem. Much more important is the aggregation of applications. This may be data aggregation, UI aggregation, sign-on integration or billing integration – and ideally users and vendors would determine what parts of the integration they bought into."

Leena Rao at TechCrunch - Intuit’s Partner Platform Goes Multilingual With Federated Apps

“The “Federated Applications” functionality lets developers who have existing SaaS applications that are built with any programming language, database or cloud computing platform publish their apps on Intuit Marketplace. Applications won’t have to be rewritten to conform to QuickBooks but will instead go through a minor configuration process.”

Phil Wainewright, ZDNet: Intuit makes two-pronged PaaS and SaaS push

“The significant element of Intuit’s PaaS announcement is that it is a land-grab to capture mindshare among developers on other cloud platforms, who can take their AppEngine, Amazon Web Services or self-hosted applications and make them available using Intuit’s single sign-on, billing and QuickBooks integration infrastructure. Market reach being one of the key attributes developers look for in a new platform, perhaps the most appealing factor is that applications will be showcased within the Intuit Marketplace, with a potential reach to the four-million-strong installed base of QuickBooks accounting software customers and their estimated 25 million employees.”

What I've found very cool about this new Federated Apps capability for IPP is that fact that these different SaaS apps are developed on a variety of stacks and hosted outside of the IPP platform.. One of the apps is built on Java. Another is built enirely on .NET. Another is a mix of RoR and LAMP. Another built of Flex (on their own hosting environment - not IPP). If an app was running on EC2, that would work too, as would an app built on Google's AppEngine. It doen't matter - the integration points for Federated Apps are just that and pretty lightweight (one of the partners was able to turnaround the work with 1 developer in less than two weeks, including time for the technical review of the app). We made a deliberate decision to make IPP agnostic to the technology that developers want to use. Yes, we have a "native" stack also, but the options we are providing developers now means there is no technology lock-in to speak of.

Here is some more information on the details of federation and how you as a developer can get started.

Oh, and a quick plug on the talk I'll be giving on how to federate applications to IPP at the Startups and the Cloud event next week in the Boston area.

Startups and the Cloud: free event in Waltham, MA, sponsored by Intuit

alexbarnett — Thu, 28 May 2009 10:41:00 GMT

This is an event I'm helping to organize...hope you can join! From the App Gap blog:

"On June 11th we’re organizing a gathering in Waltham, MA called Startups and the Cloud to talk about how starting a successful software business has changed now that cloud computing/ platforms have become highly viable, and in some cases, essential components of a startup’s strategy.

We’re keeping it compact at about four hours and we’ve been able to pack a ton of great content in. The agenda is here, but there’s a talk with Scott Cook, the founder of Intuit, a panel of local Venture Capitalists, and a panel of local CEOs. In addition, we’ll be hosting a social event where you’ll get a chance to meet some of the top thought leaders in this new wave of innovation. It’s a great group of tech leaders and, even better, it’s free!"

See: agenda and how to register.

Joining Intuit

alexbarnett — Sun, 21 Sep 2008 22:02:00 GMT

Firstly - thanks to everyone who has reached out to me in the last three weeks via email, phone calls and comments since I shared the news of my pursuit for the next adventure - I have really appreciated everyone's support and interest in my next steps.

The great news is I'll be joining Intuit as a Group Manager working in a fast growing start-up team responsible for leading the Intuit Partner Platform. Below is a snippet and some links to blog posts and articles that should give you a fairly good idea about where my focus will be a week from now.

Although I'll be working from the Orem office (Utah) to start off with, the plan is to ultimately move to the greater Boston area - another new adventure. I've visited Boston three times in the last year or so and have loved it more and more with each visit, so watch out Boston!

This is a fantastic opportunity for me personally - the team has ambitious goals and an amazing set of existing assets to leverage (see some of the numbers below) in becoming a significant player in the cloud computing space. I look forward to sharing stories of my new journey with you.

Intuit Partner Platform Opens to Developers (Sept 15 2008)

"The Intuit Partner Platform not only gives developers the opportunity to build Web-based applications, but successful SaaS businesses by taking the complexity out of managing infrastructure, hosting, user management, integration and billing. Now developers can focus on developing innovative on-demand software solutions that solve unique and important problems for the four million small and mid-market businesses across the U.S. that use QuickBooks and the 25 million employees that work in those companies.

The platform-as-a-service offering allows developers to combine the powerful open source Flex framework and Adobe Flex Builder and the proven database of Intuit QuickBase to build rich Internet applications that work with QuickBooks data. They can also leverage Adobe AIR to provide additional desktop-like functionality in their applications, such as pop-up notifications, local file system access, local data storage, and the ability to create a fully branded user experience.

"We have now accepted more than 1,000 developers into the program and it is exciting to hear their ideas and energy about what they want to build," said Alex Chriss, business leader for the Intuit Partner Platform. "Customers will benefit greatly from the imagination and expertise that developers use to solve problems facing their specific industries." "

Web 2.0 Expo NYC - Intuit Connected Services (Sept 19 2008)
Intuit Makes SaaS Play Guns For Salesforce (Sept 18 2008)
Intuit’s flexy PaaS (Aug 14 2008)
Intuit enters the PaaS wars (April 28 2008)
Intuit’s Radical New Flex + QuickBase Cloud Platform (April 16 2008)

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.

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.

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.

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.

Ozzie's "Cloud OS" Raises More Questions than Answers

alexbarnett — Fri, 27 Jul 2007 20:04:00 GMT

Ray Ozzie's briefing this week provided quite a bit more detail around Microsoft's "Software Plus Services" strategy. It's definitely worth a read (or a look, and if you're feeling too lazy for either you can read Nick Carr's summary).

It's been a year since Ozzie took over the role as Chief Software Architect from Bill Gates, and I think it is exciting to see his influence further emerge throughout the business, architectural and experential direction of Microsoft. The 30 year old company needs this injection - a shot in the arm. And his vision is the right one. It is the only one that has any chance of seeing Microsoft through its need for growth.

However, as the Ozzie's "Cloud OS" story slowly becomes more concrete, the future influence that Microsoft will have throughout the software and internet services ecosystem is becoming less clear.

Yes, we know Software as a Service (Saas) is becoming an increasingly significant trend, and we know that the enabling role Web Services (SOAP and REST based) has to play as part of the overall move to a distributed computing model is becoming ever more central, and we know that the browser will continue to further its dominance as the primary interface between humans and data, functionality and people, but what is not so clear is how many "major players" there will be in that future, what their roles will be, nor what the roles of the "everyone elses" will be.

Microsoft Partners have been assured a place by Microsoft's side in this future, but does anyone really know? How will all this fall out? How will Microsoft's traditional partner profile fit into Ozzie's new brave future? What kind of ecosystems will emerge? Will Microsoft's ecosystem of tomorrow look radically different to its ecosystem of today? Who are the Microsoft partners of today who will find themselves competing head-to-head with Microsoft tomorrow? What will Microsoft's competition of the future even look like?

The answers to some of these question may surprise us. How many people, for example, would have imagined a just few years ago that search engine providers or an online bookseller or online university network would emerge to become a serious potential competitor in the computing and software space of Microsoft? Not many. In the second internet age Microsoft's future competition and partners can literally come from any direction at any time. And they often do. In many respects, the future looks bright, but I suspect that for many in the software / computing industry the future is also very cloudy indeed.

PaaS, more than SaaS

alexbarnett — Wed, 18 Jul 2007 15:01:00 GMT

In May 2007 I attended Salesforce.com developer conference where Salesforce SOA was announced as an add-on to the Apex platform. Industry analysts focusing on the area of SaaS considered the move as significant, but not surprising (see Phil Wainewright's take on the new in May 2007 as an example).

The game is moving on. PaaS, or "Platform as a Service" could be the acronym that defines a new web-oriented model where more than just specific vertical "services" are delivered as SaaS (e.g CRM, ERP, etc).

PaaS speaks to a more generalized services platform concept. If the "web as a platform" is the notion of multiple services in the cloud, then where does the "composition" happen? There are several Mashup design patterns to chose from. These patterns are along a continuum - from pure browser presentation mashups to client-side mashups to server-side services and data mashups (composite applications). If architecturally speaking you land in the composite applications pattern for delivering your SaaS apps, then this is where PaaS comes in.

This last week there is further evidence that Microsoft and Salesforce want to benefit from the opportunity in the power of PaaS. From SaaS out, PaaS in, by Angela Eager at CBRonline.com: Sub heading is:

"The Salesforce.com Summer '07 release is all about the platform, with software-as-a-service evolving to platform-as-a-service, a move that will antagonize and incentivize big league players Microsoft, SAP, and Oracle."

Angela's analysis includes a comparison to Microsoft's own forthcoming offering, including "Titan"

"Salesforce.com might be the first to deliver an on-demand platform but it certainly will not be the only one, and the on-demand specialist is starting to feel Microsoft's breath.

Releasing snippets of information about the forthcoming Titan offering at its partner conference last week, Microsoft chief Steve Ballmer said Titan referred to a CRM application-development platform on which developers would be able to build customized applications that could run on their servers or on Microsoft's own servers.
Although the Microsoft offering is not yet available, and even after launch it will take time for some of the planned functionality to be available such as running custom user applications within the Microsoft data center, it will be a direct challenge to Salesforce.com. With similar platform offerings, users will have a choice for the first time, which has the potential to cut into Salesforce.com's growth."

Maybe "Titan" is the news I was looking for last week, but we're seeing hints at more than just Dynamics APIs as SaaS from Microsoft. There is still no real hard news on this today, but watch out for posts by the likes of Phil Richardson, a Microsoft Program manager in the Dynamics team (and my ex-neighbor in Redmond) like this where Phil hints:

"Soon (can't say exactly when) I'll be starting to blog about Titan features....Once marketing gives the go-ahead you can expect to see boatloads of Titan content on this blog. I'll be focusing primarily on features which are targeted at VARs & ISVs - but I'll make sure to throw in some end user features."

And then Phil hints a little more this week...

"Some vendors have the 'heads in the sand' and refuse to talk services seriously (with no offering or a token offering). Other vendors only offer SaaS and trash talk those who aren't pure services players. There is no question that our industry is moving towards services and Microsoft's CRM has a strategy which is sensitive towards these industry changes. As we announced: we are using our Titan Project to create a Microsoft Hosted version, a Partner Hosted version and an On-Premise version. I use the term 'version' loosely as the final number of SKUs is up to marketing. I believe we are entering an time in the industry when customers will start moving away from self hosting 'non-unique' business functions. Anything which can be achieved by configuring on the shelf apps (like Microsoft CRM) will eventually move to hosted services (if I knew exactly when 'eventually' was I'd be a rich man). Our strategy understands that customers and partners will find themselves in varying degrees along the on-premise to hosted spectrum. Some will want everything 'in the cloud' and others will want everyone their own datacenters. Some might want to prototype in the cloud and move to on-premise etc etc. I believe vendors need to interpret these changing times appropriately for their business."

(hey Phil....trackbacks? comments? common dude!)

My take is that Phil hints to more generalized services platform concept from Microsoft. PaaS, more than SaaS.

Delivering on PaaS is hard though. Yesterday, Dan Farber's post Salesforce.com transitions to platform as a service highlighted one of the greatest challenges in this PaaS space - uptime at scale:

"Collins said that salesforce.com consistently provides above 99.9 percent availability. “Three nines is the best quality of service you can get today from any on demand player,” he said, claiming that the best deployments of Siebel and Oracle are closer to 96- to 97-percent available.
In any case, as salesforce.com scales up the enterprise and companies have more dependence than for just CRM on its platform, three nines, which doesn’t include times when the service is up but suffers performance problems, won’t be sufficient for customers who can’t afford 8.76 hours of downtime a year."

Uptime is just a small (but critical) component of the whole PaaS vision. Developer tools for PaaS is another kettle of fish (see Dana Gardner's post on Software Development and Deployment as a Service, or "SDDS" - on this topic). It's how Bungee Labs sees the future. But that's for another post.

Alex Barnett Podcasts

admin — Sat, 23 Sep 2006 19:58:00 GMT

Alex Barnett Podcasts - I like podcasting, here are the links to them.

2008 - Podcasts for the Bungee Line

Nate Bowler, CTO of @Task, July 20 2008

@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, June 20 2008

"Prior to founding MindTouch and Steve worked in advanced strategies at Microsoft focusing on distributed systems and web services. We talked with Steve about MindTouch platform, its rich set of web APIs and the implications of a programmable wiki. But 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."

Update from John Musser of ProgrammableWeb, April 14 2008

"ProgrammableWeb’s John Musser returns to the Bungee Line to give us an update on the API action of early 2008. Alex and Ted apologize for the unfortunate audio treatment to the Bungee sound in the previous episode, promising “never again!” In related news, check out the new intro music for our “Cool Web Tips” segment."

Developer Community Management with Jono Bacon, March 14 2008

"There are few developer communities as large and distributed as that of Ubuntu, perhaps the most popular brand of GNU/Linux distributions available today. Jono Bacon is the first official community manager for Ubuntu. He joins to tell us what he has learned in his 18 months of working with this vast and disparate community."

Social Design with Joshua Porter, Jan 30 2008

"Joshua Porter is a usability consultant, web designer, researcher and blogger specializing in the art of social design for the web whose experience includes five years at world-renowned User Interface Engineering. Josh’s blog (Bokardo.com) is a must-read favorite for UI and web designers and is finishing up his first book, to be published in the next few weeks (details below)."

Alan Lewis on eBay Desktop and eBay APIs, January 15 2008

"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."

2007 - Podcasts for the Bungee Line

Toby Segaran on “Programming Collective Intelligence”, December 13 2007

"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, November 17 2007

"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), October 7 2007

"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."

OAuth Podcast, with Chris Messina (aka FactoryJoe), Larry Halff (of Ma.gnolia) and Eran Hammer-Lahav, November 3 2007

"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."

Jeff Barr on Amazon Web Services (Part 1), October 18 2007

"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*."

Interview with Jeremy Zawodny of Yahoo! - Part 1 and Part 2, October 1 2007

Part 1

"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

"What Mash lets you do, Hadoop and Yahoo!'s formal involvement, the WebOS meme, something Jeremy feels strongly about :-) That was fun. Watch out for the discussion on "Meta-API Providers"... More APIs...From b2c APIs to b2b APIs, plus Pipes and democratizing the mashupshpere"

Interview with John Musser of ProgrammableWeb.com, September 19 2007

"Topics covered include Facebook APIs, Amazon's recently launched Flexible Payment Service (FPS) , Google Base, Microsoft's Astoria and relational-data-in-the-cloud programming models and services, SaaS models and API SLAs, REST vs SOAP, "Closed is Still the Old Closed" and plenty more."

-

Older podcasts:

Search & Enjoy! (Podcast) The Power of Search and Recommendation, June 6 2006

"Speakers from Microsoft, Blinkx and Last.fm discussed issues of content regarding search, recommendation, the semantic web and the ownership of data in the Web 2.0 era at Content 2.0 on 6th June 2006."

-

Microformats Podcast, March 31, 2006

"Here's a great podcast for you. All about microformats..."

Guests: Tantek Çelik, Dan Connolly and Rohit Khare. I think it's safe to say these guys know a thing or two about the web and microformats.

-

OPML Podcast, March 10, 2006

"It's all about the draft OPML 2.0 spec and a few other things thrown in such as structured blogging, OPML tools, namespaces and microformats."

Guests: Joshua Porter, Adam Green and John Tropea.

--

OPML and Reading Lists Podcast with Danny Ayers and Adam Green, Feb 12, 2006

"Last year Dave Winer started to push the idea of Reading Lists for RSS. More recently, the idea of Dynamic Reading Lists and Feed Grazing (or Grazing Lists / Glists) has been kicking around.

Its likely that Reading Lists support will become a common feature of Feed Readers / Aggregators."

Guests: Danny Ayers, Adam Green and Joshua Porter

--

Attention podcast : Attention with Steve Gillmor, Feb 08, 2006

"Steve has been leading Attention conversation for some time now. In 2003 he, along with David Sifry (CEO of Technorati), initiated the attention.xml efforts and has since taken on the role as president of the non-profit Attention Trust."

Guests: Steve Gillmor and Joshua Porter

--

MSN Search Champs podcast - Privacy conversation Jan 26 2006

"I attended the MSN Search Champs today....and what a day. Given the recent news and concerns around the data MSN Search, Yahoo and AOL provided to the government, there was a session set up where the 57 bloggers / online experts at MSN Search Champ were invited to discuss the topic with senior MSN management (Senior VP Yusuf Mehdi and VP Chris Payne)."

Guests: Fred Oliveira, Dion Hinchcliffe, Joshua Porter, Chris Pirillo, Thomas Vander Wal and Brady Forrest.

--

Attention podcast: RSS feedreaders and aggregators Jan 22, 2006

"I asked two of the RSS industry's leading lights to join me for a call and share their perspective on the question of where Attention is going with respect to RSS feedreaders and aggregators: Nick Bradbury creator FeedDemon, part of Newsgator (Nick also developed Homesite - sold to Macromedia - and Topstyle) and Kevin Burton of Tailrank (also co-founder Rojo)."

Guests: Nick Bradbury, Joshua Porter and Kevin Burton

--

Structured Blogging podcast with Marc Canter and Joe Reger, Dec 16, 2005

"You might have heard of the Structured Blogging initiative announced earlier this week by Marc Canter and others...there was certainly plenty of buzz and reaction to the news, but not all the reaction was rosy."

Guests: Marc Canter and Joshua Porter

--

Identity Podcast with Kim Cameron and Dick Hardt, Dec 09, 2005

"A couple of weeks ago Joshua and I had a conversation about attention data (as podcasts).

In that conversation we kept touching on the topic of online identities and their management, so we thought we'd invite two pioneers of the identity space, Dick Hardt and Kim Cameron, to a podcast session and discuss how they saw the connections between these two related topics: attention and identity."

Guests: Dick Hardt, Kim Cameron and Joshua Porter

--

OPML = Attention Data, Attention Engines and Tailrank, Nov 12, 2005

"Although we met briefly last week, Kevin Burton and I didn't manage to get enough time to discuss some of the things on our mind at the time, so we got a Skype call together and posted it as a podcast (.mp3, 42mb).

We focused the discussion around what he calls Meme Engines and I call Attention Engines, Tailrank (Kevin's latest project), OPML, RSS and Attention.xml"

Guests: Kevin Burton

--

Web 2.0 podcast, July 01, 2005

"Richard MacManus of Read/WriteWeb and I had a Skype chat this evening and recorded the call Talked about Web 2.0, attention.xml, a bit about RSS, APIs and more."

Guest: Richard MacManus

-

Attention podcast with Joshua Porter, Nov 26, 2005

"About OPML, Attention, and empowering people."

Guest: Joshua Porter

--