Alex Barnett blog : Programming, Dev, RIA

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.

Announcing Bungee Connect

alexbarnett — Mon, 16 Apr 2007 07:11:00 GMT

At last, I can tell you more about what Bungee Labs has been up to...

We've just announced details about Bungee Connect, a 100% on-demand web development and deployment environment that will be going into Beta phase in May.

Over the next three days at the Web 2.0 Expo 2007 and on bungeeconnect.com we'll be providing a lot more detail on exactly what Bungee Connect is, how it works and why we think it will be a big deal when we go live.

So before I go on, let me quote a couple of people who have already seen Bungee Connect in action behind closed doors. The following are from tonight's two press releases (1 and 2)

First off, Dion Hinchcliffe:

“Ajax is just the beginning of the RIA story and Bungee Labs provides the rest of the solution with a web-based IDE, on-demand scalable deployment, a well-designed community model and a built-in component ecosystem with real-world licensing options,” said Dion Hinchcliffe, ZDNet blogger; President/CTO, Hinchcliffe & Co.; and editor in chief, AjaxWorld Magazine. “Bungee Connect is a surprisingly complete one-stop shop for the RIA development, deployment and operations lifecycle.”

Next, Dana Gardner:

“Given the current disjointed state of tools, testing and deployment models, most developers find creating rich internet applications (RIAs) to be complex, time-consuming and expensive,” said Dana Gardner, Principal Analyst, Interarbor Solutions. “By combining development, testing and deployment functions into an integrated, low-cost-of-entry service approach, Bungee Connect both broadens the numbers of developers that can produce web applications as well as slashes the barriers of entry for creating innovative ecommerce services and web-based businesses."

The Bungee Labs team has been working very closely with the Amazon team (and others API providers) the last few months to make sure Amazon's web services "just work" with Bungee Connect. Jeff Barr, Senior Evangelist for Amazon's Web Services:

“Bungee Labs’ decision to make their development environment integrate seamlessly with Amazon Web Services is great news for our developer community,” said Jeff Barr, Senior Evangelist for Amazon Web Services. “AWS developers can now use Bungee Connect to directly access our services, which means they can build Web-Scale applications in an easy to use, browser-based development environment.”

Another provider of web APIs, Salesforce.com has also been working closely with the Bungee Labs engineers. This time a quote from Adam Gross, Vice President, Developer Marketing, Salesforce.com:

“Salesforce.com has demonstrated that the innovation and ideas of the consumer Internet are at the core of the next generation of business applications. Bungee Connect together with Salesforce.com’s Apex platform makes it easier for developers to create mashups for their businesses, and in doing so hastens the transition from traditional enterprise software to the new on-demand model of building and deploying applications.”

So, what is Bungee Connect? Well, it's a lot of things:

Bungee Connect is a completely web-based integrated development environment (IDE) for building and deploying rich Ajax web applications, from simple web apps to seriously sophisticated Ajax applications. No install for developers, no installation of delivery infrastructure, and no client install for end users.
Bungee Connect is for developers, not for consumers. Yes, it provides a huge amount of automated support for the integration of SOAP and REST-based web services, Ajax app development and state management. You can develop sophisticated apps that integrate powerful (as well as simple) web services plus develop your own logic without having to write a line of code. It massivley reduces complexity. But, nonetheless, it is for developers, not consumers.
Bungee Connect provides a completely integrated means of deploying apps to the live web. No FTP. No separation between your dev, staging, production and live environment. No local set-up on your machine. No bits to install anywhere. No web servers, no app servers, no stacks, nor libraries to install, patch or manage. No 'Yak shaving'. It's all taken care of for you. You develop your app through the browser, then deploy your app through the browser and map the app to your domain / URL (or embed the app in your site) - It's your app. Oh, and you get IE, Firefox and Safari cross-browser compat taken care of too - you build your app once and it just works in these three browsers. Sweet.
Bungee Connect includes a whole code share and team collaboration concept. You can keep your code proprietary, or you can share it with other Bungee Connect developers in your workgroup or with the wider Bungee Connect developer community. There's a lot more to this than I can cover here and I'll be writing a lot more on this soon, but I like how Mat Asay described the community aspect as a 'Sourceforge for the 21st Century'.
Bungee Connect allows developers to leverage the world of web APIs. We've been working with the API engineering and evangelist teams at Amazon, Ebay, Google, Microsoft Windows Live, PayPal, RealNetworks, Salesforce.com and Yahoo! to ensure Bungee Connect works sweetly with the multitude of their rich APIs (both WS* and RESTful). The aim is to ensure Bungee Connect can work with any web service that you choose and by working with these teams and their APIs in developing Bungee Connect, we've got a great test-bed to make sure we can achieve this goal.
Bungee Connect is No Fee for the developer to use in developing and testing Bungee-powered apps. You only pay once you've deployed your app commercially or unrestricted. We expect this to be US$1 per computer-network-interaction-hour, billed monthly. Again, more on this later.

And there's so much more. Tomorrow, anyone attending Web 2.0 Expo will be able to get hands on with Bungee Connect. We've got a booth with PCs (Windows, Macs and Linux) with the browser open (IE, Firefox and Safari) where you run through some tutorials and judge for yourself if you think we're all smoking crack (see pics below - no crack, just the booths). We'll also be updating the site with screencasts and plenty more details and Martin will be presenting and demo'ing with Brad on Wednesday morning. And by then I'm sure David might have something more to say too...

To underline a couple of points here: we're not live yet. We go into Beta in May and are looking for web developers who ideally already have experience in progamming against the APIs of the companies I mentioned earlier. So sign up if that sounds like you...

---

Update:

Dana Gardner has written up his thoughts on Bungee Connect.
Short but sweet mention on Mashable.com by Pete Cashmore.

Update 2 (4/18/07)

Richard MacManus blogged it over at Read/Write Web
Ryan Stewart blogged us too :-)