Monday, December 14, 2009

Where To Hide a Dead Horse and Other Uses For the Cloud

With full credit to the Geek and Poke blog, the funniest nerd cartoon I have seen all year!

Wednesday, December 09, 2009

Cloud Computing - It's The Destination, Not The Journey

I have had some interesting conversations recently with partners about how cloud computing will affect the developer tools market.

I don't believe developers jump on a band wagon just because they like the wagon. They jump on the wagon because they like where the wagon is going!

Roughly every 10 years, a technology disruption changes developer aspirations and drives them to adopt new tools that get them to new places.

With client/server, developers aspired to build "modern" apps and break free of the bureaucracy of central IT. Cloud computing offers a similar, updated, value - deploy web applications without the hassle of central IT.

Developer aspirations are changing - this is the underlying market driver for WaveMaker.

At the same time, IT vendors are seeing their value disrupted. As the data center morphs into a set of APIs, decisions which used to be made by sys admins and DBAs are made by the developer (Cloud Foundry is a good example of this).

The developer platform is becoming the control panel for the data center - this is the WaveMaker's value to partners. This is also the basis for our cloud quick start program with IBM, Amazon and RightScale.

One company that has realized the competitive opportunity in cloud computing is Microsoft. By integrating Visual Studio with Azure, they have created a powerful engine from which to attack the entire data center infrastructure.

If business developers really do "take to the clouds", the challenge I see for IT infrastructure providers is how to harness changing developer aspirations to ensure that the cloud deployment stack includes their solutions.

Wednesday, November 25, 2009

A Few Things To Be Thankful For

Before I head off for my favorite holiday, I wanted to send out an update on Wavemaker.

Our big news of course centers around the release of Wavemaker 6. This release was over a year in the making and represents the first open source cloud development platform on the market (hook up wavemaker with eucalyptus and you have your own open source answer to and Azure!).

On the business side, WaveMaker continues to drive strong revenue growth in a down economy, putting us in reach our objective to achieve profitability by the end of the year!

Just to brag a bit, here are some analyst quotes from our WaveMaker 6 press release:

  • "WaveMaker's open source cloud development platform provides an important approach for customers adopting cloud computing," said Judith Hurwitz, author of Cloud Computing for Dummies and President of Hurwitz & Associates. "WaveMaker's ability to create partnerships with IBM, Amazon and RightScale also illustrates the value of an open source business model."
  • "WaveMaker is easing the migration path for Java developers who want to bring existing application logic and data into a SaaS environment, while still retaining control over their deployment options," said Phil Wainewright, industry analyst at Procullux Ventures. "With automated support for robust multi-tenant databases, WaveMaker 6.0 advances software developers even further along the path towards realizing the full benefits of the SaaS model."
  • "Cloud computing is fast maturing, but one lagging indicator is developer tools designed specifically for cloud deployment," said James Governor, principal analyst at RedMonk. "WaveMaker aims to change that with their 6.0 release, an open source toolset, and relationships with key players such as IBM, Amazon and RightScale."

Wednesday, November 18, 2009

WaveMaker 6.0 SaaS-enables Web Apps in Minutes

Until today, web developers creating SaaS apps have been faced with an ugly choice: use proprietary development platforms like or build an open solution from scratch.

WaveMaker today released the first open cloud development platform. WaveMaker 6.0 is a visual development platform that runs in a browser.

WaveMaker makes it ridiculously easy for anyone to prototype, develop and customize great looking web applications.

How easy you ask? Well, how 'bout:
With all this open and cloudy goodness, it is not surprising that the momentum behind WaveMaker continues to build.

What kind of momentum? Well, how 'bout:
Let the fireworks begin!

Wednesday, November 04, 2009

Vendors Will Have To Climb Higher To Reach Clouds

Hard on the heels of the VMWare/SpringSource acquisition, VMWare entered into a grand alliance with Cisco and EMC (although technically, VMWare announcing an alliance with EMC is like Buick announcing an alliance with GM).

Once the data center is fully virtualized, resilient and automated, it becomes the proverbial black box. As long as it is secure and performant, where it is located or what the hardware layer looks like is unimportant.

Any company whose value proposition is centered around feeds and speeds is going to have to scramble higher up the stack. If your target customer is hardcore data center guys, you are going to find fewer and fewer of those folks to talk to.

As customer IT shifts from hardware to solutions, vendors will have to climb higher up the value chain to keep engaged with their customers. With its Unified Computing System, network vendors like Cisco are becoming data center solution vendors. With Spring, virtualization vendors like VMWare are becoming development solution vendors.

At the top of the cloud stack is Platform as a Service (PaaS), which manages both how applications are developed and how they can be customized by end users. At WaveMaker, we see PaaS as the primary lever for delivering value from the cloud.

As IT vendors climb higher to deliver more complete solutions to their customers, PaaS will emerge as the heart of the cloud ecosystem.

Thursday, October 15, 2009

Ecosystem is the Killer App for Cloud Computing

We know all about these loose ecosystems of Barney-loving, hand-holding, kumbaya-singing companies who promise a full solution to help you take advantage of the next overwhelming wave of technology...for a fee.

In the past, vendor ecosystem announcements indicate a vague intention on the part of the vendors to do something together someday - providing they can all find a customer to pay for it.

With the cloud, however, ecosystems are different. They are easier to create, both from a business and technical point of view. They are also much more transparent, as the results of their efforts are available for the whole world to see.

WaveMaker, RightScale, IBM and Amazon just announced their own cloud ecosystem. This ecosystem is being marketed as a cloud quick start program, which aims to make cloud computing ridiculously easy and give companies a one-stop solution for migrating existing Java applications to SaaS and cloud computing.

Not only are all of the cloud quick start products fully integrated and running today in the Amazon cloud, but the integration is available for anyone to use who has an Amazon account. Even better, the first company to complete the 2 day cloud quick start program, KANA, was so impressed with the results that they plan on going live with their first cloud deployment before the end of the year.

What makes the cloud unique is not the individual bits of software running in some dark data center, but that for the first time it is easy to stand up a number of complex pieces of software, knit them all together and make the resulting integrated solution available to anyone who wants to use them.

Take for example the elements of the cloud quickstart program, which integrates products from four enterprise software companies. Just imagine trying to pull off this kind of integration without the cloud.

First of all, you would have to get software licenses from each vendor, then find a place to install them all and then figure out how to integrate them. These tasks alone would take weeks to months.

Now compare that with the same scenario in the cloud. WaveMaker, RightScale and Amazon already have software running on Amazon EC2 and available for anyone to use. Once the companies have done the basic integration work, it is easy to produce custom AMIs that provide a pre-integrated solution to the rest of the world.

The cloud quickstart program for cloud application development from WaveMaker, RightScale, IBM and Amazon is not the only example of this kind of ecosystem. An equally impressive ecosystem for cloud business intelligence launched a little over a month ago featuring RightScale, Jaspersoft, Talend and Vertica.

Cloud hosting providers like Amazon provide a sort of global workbench on which software vendors can integrate quickly and without even having explicit business relationships. This may in the end prove to be the real killer app for cloud computing - the ability to adopt entire software ecosystems with the click of a button.

Thursday, October 01, 2009

What Separates A Cloud From (water) Vapor?

I spoke this morning with the cloud evangelist for a hardware manufacturer. Not surprisingly, they come at cloud from the iron up, so for them cloud is mostly about virtualization with a little more buzz.

While I can understand this viewpoint, if today's cloud is just yesterday's server consolidation in new clothes, then Larry Ellison's latest "a cloud is just water vapor" rant is probably appropriate.

So what exactly is the dividing line between virtualization and true cloud goodness? I think the key lies in bringing together a fuller solution with a cloud platform than with a virtualization platform.

Cloud computing gets interesting when the platform includes not just deployment (infrastructure as a service or IaaS) but also development (platform as a service or PaaS). Linking these two capabilities opens up fundamentally new markets as well as compelling economics.

Virtualization is about abstracting application deployment so that one box can run many apps, with each app pretending that it is lord and master of it's virtual computer. The value of virtualization is to reduce the amount of hardware needed to run a set of apps and correspondingly reducing the amount of systems administration time needed to manage the overall data center.

Cloud computing is about abstracting application development and deployment so that anyone can develop and manage applications without needing specialized expertise. The value of cloud computing is to reduce all IT costs while increasing organizational flexibility. More people can build the apps they need and fewer expert developers, DBAs and systems administrators are needed.

At its core, virtualization improves IT efficiency - doing traditional computing with fewer resources. On the other hand, cloud computing improves IT effectiveness - empowering more people to build applications with more flexibility and fewer experts. For example, this is the core value prop behind IBM's Cloud Quickstart Program, which includes IBM, Amazon EC2, WaveMaker and RightScale.

Our view at WaveMaker is that the big private cloud payoff comes only when you make both development and deployment of web apps radically easier (cloud-ready computing). If you will, virtualization and private cloud management (IaaS) both reduce the administration costs - the cost transformation comes when you slash not just administration but also development and maintenance costs (IaaS + PaaS).

Wednesday, September 23, 2009

A Radical Transformation - Running Chrome Inside of Internet Explorer

Internet Explorer, particularly versions 6 and before, are the bane of any web developer's existence. The Internet Explorer versions Microsoft produced during the competion-free era between when Netscape died and Firefox came on the scene are masterpieces of monopolistic neglect. IE 5 and IE6 are slow, proprietary and just plain awful to work with.

Worst of all, Microsoft guaranteed themselves longtime domination of the corporate browser market through this cynical behavior because all the web apps built for IE 5 and 6 are so full of hacks that they won't run on "modern" browsers!

Nothing strikes fear into the heart of our professional services team quite like the words: "yeah, we're thinking about rolling out IE 7 sometime in the next 18 months."

But now there is a way out of the nightmare that is IE. Alex Russell at Google (of Dojo Toolkit fame) has figured out a way to run Chrome as a plug-in inside of IE - even the old versions. This means that web developers can build applications the way nature intended and IE is none the wiser.

For cloud computing in general and Platform as a Service in particular, this is great news. With Platform as a Service (PaaS), you develop and deploy apps from within your browser, so the power of the browser directly governs the power of the your development platform.

For WaveMaker and other PaaS vendors, this extends the reach of our cloud computing solutions to the back hinterlands of corporate America where technological change comes most slowly and where consequently frustration with IT is highest.

Thursday, September 17, 2009

Making Cloud Computing Ridiculously Easy

With all the hullabaloo about cloud computing, it is easy to get caught up in the trend of the day and miss the big picture. The big picture is that cloud computing disrupts the data center world by slashing the capital and skills required to deploy a web application.

If that is the big prize, then most of what passes for news in cloud computing is more along the lines of "me speak cloud too."

Today, cloud development and deployment is still the exclusive domain of highly paid web experts and just as highly paid hosting providers and systems administrators. As much as cloud providers like Amazon and Rackspace have done to simplify web hosting and eliminate people from the equation, it still takes far too much expertise and effort to get applications built and deployed in the cloud.

The goal of cloud computing is to make web development and deployment something that any bum can do and charge in on their credit card with nary a care in the world.

With all due humility, I think RightScale and WaveMaker have taken a big step towards that goal this week, introducing an easy-to-use cloud development platform with one-click deployment to Amazon EC2 via RightScale.

It is now monkeys-on-keyboards easy to create a web application and deploy it in a secure, scalable cloud environment using WaveMaker/RightScale and Amazon.

So who cares about this stuff anyway? How 'bout IBM and Amazon!

On Thursday, October 1, IBM and Amazon are hosting a half-day webinar entitled Cloud computing for developers: Hosted by IBM and Amazon Web Services . At that webinar, WaveMaker and RightScale will provide an online demonstration of building a web application with WaveMaker and deploying it to a WebSphere AMI using RightScale. One small click for man, one giant cloud for mankind!

Thursday, August 27, 2009

Cloud Ready Computing

Cloud computing offers significant economies in deploying and managing applications. While enterprises are not yet ready to move mission-critical applications to cloud computing, CIOs and CTOs are increasingly wanting to create applications that are "cloud-ready."

A cloud-ready application is based on an architecture which provides the flexibility to deploy the application to either a traditional data center or into a private or public cloud infrastructure. This flexibility ensures that enterprises can take advantage of cloud computing benefits whenever they choose.

Being cloud-ready requires much more than simple virtualization. As the $420M acquisition of SpringSource by VMWare demonstrates, making applications cloud ready requires adopting new development platforms that are purpose-built for supporting on-site and on-demand computing.

Some cloud-ready development platforms (also called Platform as a Service or PaaS) are highly proprietary. These frameworks require a complete rewrite of the application for cloud computing and lock the developer into a single hosting provider such as SalesForce or Google's AppEngine.

Other cloud-ready development frameworks are open, enabling developers to leverage existing application logic and data. Open Platform as a Service, or OPaas, allows CIOs and CTOs to have the best of both worlds, creating applications which can run in the data center or in the public cloud with no changes to the underlying application. Examples include WaveMaker and Corent.

Cloud Ready Case Study - IBM's Cloud Quickstart Architecture

IBM has created a Cloud Quickstart Architecture that embodies what they see as best practices for developing cloud-ready applications. This architecture includes WaveMaker, WebSphere, DB2, Amazon and RightScale. To see a podcast on this architecture, click here (registration required).

WaveMaker is an Open Platform as a Service for developing cloud-ready web applications. WaveMaker includes client and server frameworks that greatly reduce the time to cloud-enable an existing application or create a new, cloud-ready application.

The WaveMaker self-service client framework provides configurable, drag and drop client components that simplify the delivery of self-service web applications. The WaveMaker multi-tenant server framework provides secure, multi-tenant server modules that automate the creation of scalable cloud applications.

The WaveMaker frameworks are backed by a 10,000-strong developer community and complement existing application servers (e.g., Tomcat, WebSphere) and development tools (e.g., Eclipse, Netbeans). WaveMaker customers like KANA, National City Bank and Macy's have cut the cost and time to build cloud-ready applications by over 75% using WaveMaker.

In the IBM Cloud Quickstart Architecture, ISVs can leverage existing Java code written in WebSphere as well as data stored in DB2. WaveMaker provides the cloud-ready frameworks for the client and server. RightScale provides elastic scaling as well as fault tolerance and fault recovery. Together, these companies provide an example of end-to-end cloud computing that leverages existing application resources.

Tuesday, August 11, 2009

Why VMWare Bought SpringSource

VMWare announced a $420M acquisition of SpringSource today. Given that SpringSource revenues are estimated to be around $20M, this acquisition was a spectacular validation that cloud computing is rearranging the development landscape.

SpringSource developed the Spring open source Java application platform. Over the last year, SpringSource also acquired the Tomcat web server and Hyperic management tools, giving them a complete platform to build, run and manage Java applications.

SpringSource shares WaveMaker's vision that the future of cloud computing belongs to open platform as a service products. Many cloud solutions today are completely proprietary, locking developers into a single vendor.

In contrast, SpringSource and WaveMaker both promote an Open Platform as a Service vision. By providing an open platform for both cloud and data center hosted applications, SpringSource and WaveMaker give developers flexibility to build and deploy applications wherever they want.

With this acquisition, VMWare will be able to optimizes the services it provides based on a better understanding of how the applications themselves are built. With cloud computing, the age of generic virtualization is coming to an end. Hosting providers who can optimize their services based on application-specific requirements will have an advantage over "application-blind" hosting providers.

As cloud computing disrupts the way applications are deployed, it is also disrupting the way applications are developed. At WaveMaker, we believe the next big step is for the development tool themselves to move into the cloud, making it possible to build and deploy applications completely from a browser.

More resources
Matt Assay's analysis of the VMWare acquisition on CNET

Rod Johnson's blog post on the VMWare acquisition of SpringSource

Thursday, July 23, 2009

Survey: IBM ISV Plans for SaaS Development

recently held a joint webinar with IBM to describe a methodology for ISVs to migrate to SaaS and cloud computing cost-effectively (you can see the recorded webinar here). The key is being able to leverage existing data and logic while moving iteratively to deliver web, SaaS and Cloud capabilities that provide the biggest value to the customer at the least cost and risk to the software developer.

During the webinar, we conducted a survey of the ISV attendees that turned up some interesting results about where ISVs are along the SaaS migration path and where they would like to be in 12 months.

We defined a SaaS maturity model with 5 levels:
  • Level 0: web-enabled. The ISV's application can be accessed through a web browser without requiring the end user to install anything on their desktop.
  • Level 1: hosted. The ISV's application can be hosted without requiring the customer to install anything in their data center.
  • Level 2: self-service. The end user can customize an application (e.g., configure dashboards, reports, data, workflow) without having to do any coding.
  • Level 3: multi-tenant. The ISV can support multiple customers with a single application, database and security instance.
  • Level 4: cloud scalable. The ISV can deploy their appplication within a cloud infrasctructure that automatically scales up and down based on load.
The interesting thing about this maturity model is that levels 0 - 2 are about delivering higher value to the ISVs customers, while levels 3 and 4 are about reducing costs to the ISV to scale their operations. The important take away for the ISV is that the value of levels 3 and 4 are highly sensitive to the ISVs projections about the number of customers they need to support along with the level of customization that each customer requires.

Based on this maturity model, attendees first told us where they are today. The following pie chart shows how ISVs rank the maturity of their existing products. Note that over half of the ISVs put themselves at the most basic level - web-enabled application.

Next, we asked ISVs where they would like to be in 12 months. The following pie chart shows where ISVs would like to see their product offerings in 12 months. Note that the bulk of ISVs intend to deliver self-service customization, but fewer ISVs plan on moving all the way to a multi-tenant, cloud-scalable solution over the next 12 months.

Admittedly, this survey data is more anecdotal than rigorous (there were only 35 respondents). However, it is an interesting indication that ISVs are looking for an incremental methodology for migrating their applications to SaaS, rather than a big bang approach in which the ISV does a complete rewrite of their software.

  • Click here for more about IBM's SaaS enablement program
  • Click here for more about the SaaS maturity model

Wednesday, July 08, 2009

Another SaaS Migration Success For WaveMaker

In addition to growing sales by a whopping 80% last quarter (worthy of another blog post on its own no doubt), WaveMaker also brought on a number of impressive new customers.

Yesterday we announced that the ECN Group subsidiary of New Zealand Post has adopted WaveMaker as their platform for delivery the next generation of their Round Trip Logistics application. ECN has over 3,000 customers and sells their SaaS logistics application throughout New Zealand, Australia and Asian markets.

WaveMaker makes SaaS simple both for SaaS vendors and their customers:
  • SaaS migration: like many ISVs, ECN already has a good deal of application business logic written in Java. WaveMaker allows ECN to create a new SaaS application that leverages the work they have already done.
  • SaaS development: just like we did with KANA 10, WaveMaker's drag and drop development platform can cut the time to develop a new SaaS application by at least 50%
  • SaaS end-user customization: WaveMaker's unique strength is in enabling SaaS vendors to deliver applications that can be easily customized by end users. In KANA's case, this meant enabling business managers to react to changing business conditions by customizing workflows in minutes that would otherwise take months of expert IT resources.
WaveMaker's SaaS development platform shows ISVs how to build a SaaS application using an incremental approach that delivers the highest bang for the buck. Other solutions like require that ISVs completely redevelop their application - a more costly and risky approah.

Wednesday, July 01, 2009

KANA 10 - New Poster Child For Web 2.0 Self-Service

Yesterday, KANA announced the release of KANA 10, whose killer feature is the ability for call center executives to do self-service customization of call center workflow to meet changing business requirements.

KANA is using a customized version of WaveMaker studio that allows call center execs to configure the business workflow using a drag and drop interface.

KANA 10 shrinks a process that used to take months down to minutes - all thanks to WaveMaker!

According to KANA's CTO, Mark Angel, "WaveMaker's visual Ajax studio turbocharged our web development effort for KANA 10, cutting at least 50 percent of our UI development time compared to a standard Ajax library."

The following screenshot shows an agent dashboard built using WaveMaker and based on the Dojo Toolkit. Pretty snazzy huh?

The following screen is intended for end user self service and gives proof positive that Web 2.0 has entered the enterprise!

KANA 10 was built using WaveMaker and the IBM SOA Foundation and was developed in conjunction with IBM customers. KANA did a complete rewrite of their entire suite of applications in less than a year (we announced the WaveMaker/KANA deal 10 months ago)- a terrific validation for Web 2.0, the Dojo Toolkit, Ajax and SOA technologies.

Thursday, June 25, 2009

Big Hairy Severed Jugulars - and other secrets of marketing new software products

While our engineering team works feverishly on the Beta 2 release of WaveMaker for the cloud (with intermittent breaks for foosball), I am wrestling with how to explain what our product does and why anyone should care.

Let's face it - small, innovative tech companies are a dime a dozen. When we ask potential customers to literally bet their careers on our latest shiny gizmo, there had better be a pretty compelling reward to offset that risk.

With that in mind, I am creating a marketing pitch to overcome customer's innate skepticism by answering three basic questions:
  1. What is the severed jugular customer pain point? The first step is to identify a customer problem that you can solve and that customers really care about. Solving an annoying problem works for established vendors (kind of), but absolutely will not get a new vendor in the door. The marketing pitch has to solve a top 3 problem where the customer believes "if I don't get this resolved my job is on the line."
  2. What is a unique selling proposition? Connected directly to the pain point, you have to define exactly what unique benefit the customer can only get from your product. The important point here is that there is a single unique value that you will put first and foremost in front of the customer.
  3. What is our company's big hairy audacious goal? Even if a customer has a huge pain point and sees the value of your unique selling proposition, they will only buy if they think you will be around long enough to solve their problem. In this case, "solve their problem" means that the customer gets so much glory for choosing your product that they get promoted (at which point it's the next guy's problem ;-). Creating a big vision for your tiny company is a powerful way to give your customer confidence that your product is around for the long haul.
This of course sounds more formulaic than it actually is, but at a minimum provides some good questions to ask when evaluating a marketing pitch. Stay tuned for WaveMaker for the cloud's answers to these questions!

Thursday, June 04, 2009

Twitter is AIM for adults

At the monthly NVMDA* last night, the topic turned (as all tech topics do these days) to Twitter.

What those of us with teenagers reported is that Twitter is a complete non-phenomenon for the otherwise technologically-obsessed younger generation.

Our conclusion was that Twitter is most exciting for people who don't use instant messaging. To be sure, Twitter != AIM and vice versa, but Twitter provokes a fascination with instant communication among older geeks that younger geeks like my son experience every day via text messaging.

Not that this necessarily spells any sort of dire outcome for Twitter, just that it is unlikely to replace SMS as the communication vehicle of choice for the next generation of computer jocks.

* Noe Valley Men's Drinking Association, a poorly, but aptly named group of thirsty gentlemen.

Friday, May 22, 2009

Oops, my inner nerd is showing

With the release of WaveMaker 5.0, I rolled up my sleeves, got out my pocket slide rule for moral support, and dove into tech-topia.

The result was two very geeky articles:
Both articles were well received - even the notoriously testy ServerSide crowd was well behaved.

The down side, of course, is that programming plays to my built in compulsive/addictive personality, so I find myself waking at 2am with my brain working on some minute programming problem in full throttle.

Monday, May 11, 2009

The Missing Link - Data Access for RIAs

ZapThink just produced a good report on the state of Web 2.0 tools entitled "Evolution of the Rich Internet Applcation Market."

In the report, Jason Bloomberg and Ron Schmelzer of Zapthink highlight a critical gap in most RIA solutions: the inability to access data from within the UI. They then point to this as a major source of competitive advantage for Adobe:
"Adobe stands alone as the only vendor who offers a commercial, RIA-specific data access product."
It is probably not completely fair to expect Zapthink to include in last week's report a product that was released last week, this is exactly the problem that WaveMaker 5 solves with Enterprise-ready Data Widgets. In fact, the similarities between Adobe and WaveMaker's solutions is startling:

Comparison of RIA Data Frameworks

The Zapthink report concludes by saying that the most attractive market opportunity is not for stand-alone RIA libraries but for full RIA development enviroments like Adobe LiveCycle, Microsoft Silverlight and WaveMaker.

Friday, May 08, 2009

Five Free Mashup Tools You Should Know About

Mashups is a pretty broad term. A good definition for a mashup tool is a solution that allows developers to combine interesting data and then visualize that data through a web application

Usually, mashups are web applications that can be created quickly using standard web services (e.g., REST) and components (e.g., Widgets).

There are three kinds of Mashup tools: front end, back end and integrated. The differences are:
  • Front end mashup tools: these tools help build web front ends like dashboards using widgets/gadgets and little to no programming (iGoogle, PageFlakes)
  • Back end mashup tools: these tools combine web-accessible data and services into more useful web services that can be called easily using a REST-ful interface (Kapow, Yahoo pipes)
  • Integrated mashup tools: these tools make it easy to build end-to-end web applications that link web widgets to data and services.
When evaluating mashup tools, you need to think about what kind of mashing you are trying to do:
  1. Do you want to create a visual dashboard from existing widgets? Try a front-end mashup tool. These tools make it easy to create a personal dashboard that tracks your stocks, local weather, the time in 51 timezones and the current price of titanium.
  2. Are you wanting to turn web-accessible stuff (like ebay auctions or linkedin contacts) into a web service API? Try a back-end mashup tool to get at data programmatically that you otherwise have to do by hand (and mouse).
  3. Do you need to create an end-to-end web app like a dashboard or simple business portal? Try an integrated mashup tool to build applications quickly and with minimal programming. Integrated mashup tools are effectively the modern version of MS Access for the web.
Another factor to consider is whether you have to download and install anything to use it. Mashup tools can be purely web-based (like Yahoo pipes or PageFlakes), purely download (Open Kapow) or available both as a download or hosted (like WaveMaker and IBM Mashup Center, both of which are hosted on Amazon EC/2).

Here are five free, open source mashup solutions you might want to check out:

iGoogle - Front End Mashup Screen Builder Tool

If you are looking for lots and lots of widgets, look no further. iGoogle has tens of thousands of gadgets (many of the most popular ones NSFW, but that's how it goes). Try iGoogle here.

Open Kapow - Back End Mashup Service Builder

The web is a wonderful place to find information, if you are a human and have a lot of time. Getting programmatic access to data on the web is a completely different story (wouldn't it be nice to see which of your favorite restaurants has a table open at 6 tonight automatically?) Kapow is a web-based tool for creating "robots" that gather data on the web and return the results as a web service. Try open Kapow here.

Yahoo Pipes - Back End Mashup Service Builder

Pipes is a web-based tool that allows developers to aggregate, manipulate, and mashup content from around the web. It is not as full-featured as Kapow, but you can try it without having to download anything. Try Yahoo pipes here.

IBM Mashup Center - Integrated Mashup Builder

Mashup Center was written with the non-developer in mind. That design objective increases the number of people who can use the tool, but limits the complexity of what you can build. In general, Mashup center requires that developers create a set of enterprise widgets (using IBM's iWidget spec) . There is also a cloud version of Mashup Center, but it requires that you have your own Amazon account set up. Try Mashup Center here.

WaveMaker Studio- Integrated Mashup Builder

WaveMaker provides a fast and easy way to build web applications. It targets Java developers who want a RAD GUI builder as well as novice web developers who want to build web applications with minimal learning curve. You can try the cloud version of WaveMaker here, or try the WaveMaker download here.

Monday, May 04, 2009

WaveMaker 5 Cuts Java Web Development Time 90%

Today, we launched version 5 of our visual development platform for Java and web developers.

Java developers need the equivalent of MS Access for building Java Web Applications. Currently, a Java developer wanting to build a web application faces a huge learning curve, to say nothing of the coding burden.

WaveMaker 5 addresses the need for easy to use tools for building Java Web Applications. Wavemaker 5 introduces Enterprise-ready Data Widgets. WaveMaker generates these custom components automatically when a developer connects to a database.

With Enterprise-ready Data Widgets, WaveMaker reads the database schema and creates a widget for each table that the developer can drag and drop into an application. Enterprise-ready Data Widgets can display table data as an Ajax grid or as a form with automatic data validation and built in create, update and delete capabilities.

WaveMaker makes it possible for a developer to create a database-driven web application with literally three clicks:
  • Click 1: connect to the database. WaveMaker studio automatically imports the schema and creates an Enterprise-ready Data Widget for each database table.
  • Click 2: drag Enterprise-ready Data Widget from the studio palette to the application canvas
  • Click 3: press Run to perform a test run of the application in a local Tomcat server. The final application can deploy to any Java server.
Try it today! You can download WaveMaker and try it yourself here.

Wednesday, April 22, 2009

WaveMaker Weathers The Storm

In my various swims around the San Francisco bay, there have been times - thankfully only a few - when the combination of waves and tide seemed too powerful to overcome. Luckily, I have yet to get swept out under the Golden Gate bridge.

In a similar way, there have been economic times - again only a few - when the combination of customer caution and investor panic seemed overwhelming. Through Q4 and Q1, our strategy was to hunker down, dig deep and do our best.

As it turned out, doing our best and not losing focus was enough to help WaveMaker grow revenue through the last six months. More importantly, we are closing in on our goal of profitability for the second half of the year.

In my experience, startup companies always seem incredibly fragile, but are actually pretty resilient. Of course, it helps to be solving a pressing problem in a growing part of the market ;-)!

I am particularly excited about our upcoming WaveMaker 5 release this month. This release sets a new gold standard for ease of use: you can build and deploy a complete, database-driven web application in just 3 mouse clicks!

Here are some of the continuing signs that WaveMaker has the current in its favor:
  • Huge ROI Proof: Judith Hurwitz wrote a report as part of IBM's SaaS Enablement practice, showing how using WaveMaker can lower SaaS TCO by 75%
  • IBM Partnership: WaveMaker is providing integration tools for IBM's LotusLive, for example adding SalesForce and LinkedIn contacts to the LotusLive dashboard.
  • Agile Services Launch: WaveMaker now has its own crack services team. Need a web solution built quickly and cost-effectively? Call us!
Here's hoping that the worst of the economic storm is behind us and that smoother waters lie ahead.

Wednesday, April 08, 2009

Opening Up Platform as a Service - What is Open PaaS?

Platform as a Service (PaaS) offers a way to build and deploy applications entirely in the cloud. This market was pioneered by SalesForce and their PaaS offering.

PaaS offers the potential to democratize web development by enabling anyone who can use a browser to assemble and extend web-based applications. Yet early PaaS players, including, Bungee Labs, Google AppEngine and Microsoft's Azure, have introduced PaaS solutions that are remarkably proprietary.

A proprietary PaaS solution introduces high switching costs to move data or logic from one PaaS provider to another. For example, moving an application from the recently deceased Coghead to AppEngine would require a wholesale rewrite of an application written on one proprietary framework to another.

In short, customers adopting PaaS gain access to powerful new technical capabilities but at the cost of stepping back to the proprietary business models of 20 years ago. Surely the same market forces that have driven greater transparency in the enterprise software world will also prevail in the brave new world of cloud computing!

In talking with customers and analysts, WaveMaker has introduced the term Open PaaS to describe what the next generation of cloud development tools should look like. In our definition, Open PaaS solutions have four characteristics:
  1. Portable - customers must be able to run applications built using PaaS tools on multiple cloud offerings. PaaS offerings based on proprietary languages (e.g., SalesForce, Bungee, Coghead) lock customers into a single cloud provider.
  2. Based on open standards - customers must be able to leverage existing skills such as Java and Javascript to build applications using a PaaS tool. Offerings that are based on proprietary software stacks (e.g., Google AppEngine, Microsoft Azure) lock customers into a single cloud infrastructure.
  3. Available as open source - customers must be able to run applications created with PaaS in their own data center in an open source environment . SugarCRM pioneered the attractive concept of letting the customer "take their ball and go home." For PaaS vendors, it is even more important that customers be able to move a cloud app from the cloud to behind their firewall.
  4. Mobile-aware - increasingly, web enablement reaches beyond the desktop browser to smartphones from companies like Apple, RIM and Palm. Customers need PaaS tools that can deliver device-appropriate content and functionality. Effectively, this is an update of the old Java "write once run anywhere" mantra.
As the cloud evolves, it is inevitable that customers will demand more flexibility. With that in mind, WaveMaker recently became a supporter of the Open Cloud Manifesto, a very timely effort spearheaded by Reuven Cohen, CTO of Enomaly.

You can read the Open Cloud Manifesto here, but here is my take on the 6 principles of the Open Cloud Manifesto (the bold titles and italic comments are mine):
  1. Commit to cloud interoperability: Cloud providers should collaborate to solve standard problems (e.g., security, interoperability) in a standard way. At a minimum, this requires publishing the APIs needed to build interoperable security and other services across cloud providers.
  2. Eschew vendor lockin: Cloud providers must not use their market position to lock customers into their particular platforms. This goes to the heart of the problem. If you are at the head of the pack, why slow down and let others catch you? The answer can only be because doing so gives you access to a much bigger market, of which you are still at the head of the pack but with a smaller lead!
  3. Adopt existing standards aggressively: Cloud providers must use and adopt existing standards wherever appropriate. This will be much easier for new cloud vendors, who are starting from scratch, than existing cloud vendors, who built out their infrastructure before many of these standards existed.
  4. Minimize proliferation of new standards: When new standards are needed, Cloud vendors must be judicious to avoid creating too many standards. We must ensure that standards promote innovation and do not inhibit it. This shows great wisdom in the ways of the world. What are most standards bodies anyway but the effect to gain or preserve market share by non-market driven means?
  5. Focus new standards on actual customer needs: Any community effort around the open cloud should be driven by customer needs. This is another swipe at the self-serving approaches of many standards bodies. From a cynical perspective, we will know cloud computing is successful when its standards bodies become just as opaque and non-customer focused as other entrenched standards like Java ;-)
  6. Cooperate between standards groups: Cloud computing standards organizations, advocacy groups, and communities should work together and stay coordinated, making sure that efforts do not conflict or overlap. This is well-intentioned, but also seems to be saying "thou shalt have no cloud advocacy groups before me" (shouldn't that be commandment I?)
Just like that large collection of tubes called the Internet, this notion of Open Cloud and Open Platforms is here to stay!

Wednesday, March 18, 2009

What Is Platform as a Service (PaaS)?

There are a number of companies offering Platform as a Service (PaaS), but little agreement about what PaaS is or how to compare various PaaS offerings from companies ranging from SalesForce to WaveMaker. Even the Wikipedia entry on PaaS starts with a stern warning that the entry is full of buzzwords and lacking in concrete examples.

Definition of PaaS

PaaS solutions are development platforms for which the development tool itself is hosted in the cloud and accessed through a browser. With PaaS, developers can build web applications without installing any tools on their computer and then deploy those applications without any specialized systems administration skills.

McKinsey & Company, in their 2008 report "Emerging Platform Wars," defined Platform as a service as "cloud based IDEs that not only incorporate traditional programming languages but include tools for mashup-based development."

What Makes PaaS Different?

The alternative to PaaS is to develop web applications using desktop development tools like Eclipse or Microsoft Access, then manually deploy those applications to a cloud hosting provider such as Amazon EC2.

PaaS platforms also have functional differences from traditional development platforms. These include:
  • Multi-tenant development tool: traditional development tools are single user - a cloud-based studio must support multiple users, each with multiple active projects.
  • Multi-tenant deployment architecture: scalability is often not a concern of the initial development effort and is left instead for the sys admins to deal with when the project deploys. In PaaS, scalability of the application and data tiers must be built-in (e.g., load balancing, failover need to be basic elements of the dev platform itself).
  • Integrated management: traditional development solution usually do not concern themselves with runtime monitoring , but in PaaS, the monitoring ability needs to be baked into the development platform.
  • Integrated billing: PaaS offerings require mechanisms for billing based on usage that are unique to the SaaS world.

Faux PaaS - 4 Ways To Tell If It's *Really* PaaS

At a minimum, a PaaS solution should include the following elements:
  1. Browser-based development studio - if you have to install something on your computer to develop applications, that's not PaaS!
  2. Seamless deployment to hosted runtime environment - ideally, a developer should be able to deploy a PaaS application with one click. If you have to talk to a person to get your app deployed, that's not PaaS!
  3. Management and monitoring tools - while cloud-based solutions are very cost effective, they can be tricky to manage and scale without good tools. If you have to bolt on DIY monitoring to scale your cloud app, that's not PaaS!
  4. Pay as you go billing - avoiding upfront costs has made PaaS popular. If you can't pay with your credit card based on usage, that's not PaaS!

Benefits of PaaS

The benefits of PaaS lie in greatly increasing the number of people who can develop, maintain and deploy web applications. In short, PaaS offers to democratize development of web applications much the same way that Microsoft Access democratized development of client/server applica

Today, building web applications requires expert developer with three, highly specialized skill sets:
  1. Back end server development (e.g., Java/J2EE)
  2. Front end client development (e.g., Javascript/Dojo)
  3. Web site administration.
PaaS offers the potential for general developers to build web applications without needing specialized expertise. This allows an entire generation of MS Access, Lotus Notes and PowerBuilder developers to start building web applications without the huge learning curve.

PaaS Resources

Examples of PaaS solutions today include:
  • AppEngine from Google: based on Python and Django
  • from SalesForce: based on the SalesForce SaaS infrastructure and Apex language
  • Bungee Connect: visual development studio based on Java
  • LongJump: based on Java/Eclipse
  • WaveMaker: visual development studio based on Java and hosted on Amazon EC2
Other definitions for Paas are offered by Bungee, Salesforce and ZDNet.

Monday, March 16, 2009

How to create an unbelievable amount of buzz

We were briefing a senior architect at one of our partners last week when he commented, "you know, for a company of your size, you generate an unbelievable amount of buzz." In the same week, we were flattered to have a competitor draft a lengthy blog post that listed all the reasons they were better than WaveMaker.

From the inside, it always feels like things are moving too slowly, but from the outside, clearly WaveMaker is, well, creating liquid oscillations.

Later on today, I am presenting to a group of Haas MBAs on the topics of innovation and entrepreneurship. So with my professorial hat on (and continuing my series on open source marketing metrics), here is my best guess at a stepwise approach to building buzz:
  1. Go open source to get into the game. It is amazing to me how many SaaS and cloud companies are still playing the old, proprietary enterprise software game. I believe that open source is the only viable technology channel today - without this, building buzz is almost impossible. Coghead was the latest victim of the proprietary software strategy, despite launching the first, easy-to-use cloud development platform. iPhone is a good counter-example, but Apple is a special case of a company that has always gotten away with murder because of their fanatic base of developers.
  2. Feed your community to build a fan base. Without an open source product, I would argue that it is almost impossible to create a self-sufficient community. Communities don't grow by themselves, though. It takes dedicated resources to nurture a community into a real advocate for your product.
  3. Blog your vision. Blogs provide a platform for entering into a dialogue (or at least a protracted monologue) about where the market is going. It creates a way to engage with the community and draw new people to the community. For the last 6 months, the Keeneview blog has always been the number 2 or 3 source of new downloads for WaveMaker.
  4. Twitter your tactics. Twitter provides an instant gratification approach to discussing the latest tactical nuances of your strategy. My Twitter account is where I make short, cryptic pronouncements for the benefit of all my ADHD friends.
  5. Carpet bomb your successes. Whenever anything good happens, I make sure the world knows about it. This includes not just spamming my own social media (Facebook, LinkedIn, dZone, delicious, stumbleupon) but also reaching out to all the other bloggers out there who are always looking for validation points around their own vision. For example, each time I make a blog post, I send emails to a dozen or so bloggers who I think will be most interested in it, thereby getting a multiplier effect.
  6. Brief analysts to confirm your victories. Analysts like Judith Hurwitz, Michael Cote at Redmonk, Mark Driver at Gartner and John Rymer at Forrester are critical for getting the word out, but I see their role as fast followers, not leaders of market momentum. Once you have enough proof points among bleeding edge adopters, the analysts can connect the dots for more mainstream adoption, not to mention perform major messaging tune-ups!
I'm not guaranteeing these techniques will work for everyone, but they should help get you on your way to "unbelievable" buzz!

Wednesday, March 04, 2009

How To Lose The Codies

The open source world has been very, very good to WaveMaker. We have a thriving online community, and through our community we have attracted customers like Cisco and Macy's, along with partners like IBM and KANA.

The open source world thrives on transparency and trust - a potent combination.

Yet every so often we get tempted to go back to the bad old proprietary world where decisions are made based on opacity and who you know.

With jaw-dropping naivete, I paid $1,100 to an organization called the Software Information Industry Association ( in order to participate in their Codies awards contest.

I was snowed by the idea that the SIIA's crack panel of judges performs thorough evaluations on scores of software products to glean "the best of the best." Unfortunately, the reality was much more mundane.

I don't know what process the winners go through, but I have detailed knowledge of the process for Codie losers. To help you save over $1,000 ($850 membership + $250 contest fee), I will share this process with you:

Process For Losing the Codie Awards [Guaranteed to Work]
  1. Pay $1,100 (very important!)
  2. Get assigned a judge (up to you to set up a meeting!)
  3. Set up a meeting
  4. Reschedule meeting when judge fails to show up for meeting
  5. Repeat steps 3-5 until contest is over
  6. Receive written evaluation from judge which demonstrates that they make up in chutzpah what they lack in integrity
In our case, the "judge" was Paul Cohen, who certainly didn't take off any time from his job at the Beverly Hills public schools on our behalf. His evaluation was that WaveMaker is a "very pricey set of web controls." It doesn't take great technical expertise to observe that this is an odd description of an open source, web-base IDE.

Ah, I thought. The Codie awards manager, Lisa Mitchell will help! After all, she helped arrange the meeting with the judge and knows that the promised meeting never happened. Not surprisingly, she has become as difficult to reach as our judget.

But then there is that ultimate arbiter of justice, the CEO of the SIIA, Ken Wasch. Surely when he sees how egregious our case is, he will at least agree to have another judge at least look at our product. After an initial friendly call, I have heard nothing from him either.

The process for losing the Codies is very transparent. The process for winning is less so.

It's a good thing that "who you know" awards are being replaced by the voice of the open source community. Shame on me for ever doubting it!

Wednesday, February 11, 2009

Startling scientific discovery: little vegetable bits do not spontaneously dissolve in sink

For those of you who feel that the life of a hard-charging Silicon Valley CEO is non-stop strategic wheeling and dealing, I submit the following internal memo for a more balanced perspective.

To: All SF Employees
From: Your chief executive officer and primary sink disposal unit
Re: Unwillingness of vegetable matter deposited in sink drain to spontaneously disappear

While I applaud the steadfast perseverance of our intrepid WaveMaker scientists, the fact remains that the bits of carrots left in the sink yesterday did not spontaneously vanish as was no doubt the plan. Nor did the peas left in the sink today.

In fact, vegetable and other materials larger than approximately the head of a pin are remarkably consistent in their reluctance to do anything but rest idly in the sink filter until some poor clod (usually me) comes by to clean them out.

In the future, you are more than welcome to conduct whatever experiments you want in the comfort of your own home. However, in our shared kitchen I would appreciate an approach of "nothing but water down the drain."

Thank you for your kind attention.

- chris

Friday, February 06, 2009

Good Guys - Dropping Like Flies

Sean Kerner just reported that MySQL president Marten Mickos is leaving Sun. I can't imagine worse news for Sun's efforts to buy a seat at the table for the next generation of computing.

MySQL pioneered the open source business model and is emerging as a key player in cloud computing. It borders on tragic that Sun is unable to inspire and retain executives like Marten.

I had a lunch yesterday with a good friend who is studying innovation. We compared innovation at Sun with innovation at Apple.

In 2000, both Sun and Apple got hit hard. Apple famously recovered. Sun, only somewhat less famously, did not.

Nobody claims that Sun engineers stopped innovating after 2000. It is clear, however, that Sun's management has been ineffective in harnessing that innovation to create a successful business strategy.

I got to know Marten when my last company, Persistence Software, was purchased by Progress Software. Progress was in a huge food fight with MySQL about who owned the MySQL trademark in the US - it's long story (complete with Marten being arrested by a Sherriff at the Progress headquarters), but Marten won.

Marten Mickos proved that he has what it takes to turn innovation into business success. He clearly believes that he can be more successful innovating outside of Sun than within.

Wednesday, January 28, 2009

Thriving Thru Recession With Head In the Clouds

Despite the gloomy headlines, WaveMaker is having a great year - our revenues continue to grow over 50% a quarter and we launched a partnership with IBM at last week's Lotusphere. InfoWorld continues to sing WaveMaker's praises as well.

The worldwide recession is sort of like a giant avalanche, sweeping startups and industry titans alike before its path. Having a leadership position in a rapidly growing market like cloud computing is a way to not only survive the recession but come out stronger on the other end.

Benjamin Thompkins has a good post on the bmighty blog about cloud computing as the ultimate recession-proof technology. Here are my top 3 recommendations for surviving today's economic avalanche:
  1. Stay ahead of the destruction - with the economy collapsing, the only safe place is in a market that is growing enough to dampen the blow.
  2. Don't waver in your path - survival mode is all about executing - finding ways to bring in as much revenue as possible on the path you are on. Changing course while the avalanche is bearing down on you is corporate suicide.
  3. Have friend who can help dig you out - when the going gets tough, you soon find out what kind of investor support you have. All VCs are easy to work with when times are good - it is the behavior of VCs in the bad times that separates the bankers from the builders

Thursday, January 22, 2009

IBM Gets Seriously Social with WaveMaker

WaveMaker shared the stage this week with LinkedIn, SalesForce and Skype at IBM's launch of their new collaboration platform, LotusLive. Appropriately enough for a new entrant in the Serious Social market, Lotus Live launched at the Disneyworld resort in Orlando.

Clint Boulton of eWeek had a good description of LotusLive:
"LotusLive is the brand name for meeting, messaging and collaboration applications IBM intends to deliver to partners, who will in turn put them in front of their customers as a SAAS (software as a service) platform this year"
Sean Poulley, the Vice President of Collaboration Services, was the emcee for the very entertaining LotusLive launch presentation (it's not often that you see Crocodile Dundee used to promote cloud collaboration).

After producing a great deal of vapor around the somewhat suspect term Web 2.0 and the even more dodgy term Enterprise 2.0, IBM and LotusLive are finally validating the premise that social networking will be as powerful a force in the enterprise as it has been for the consumer world.

WaveMaker's 15 minutes of fame came via a Social Network Integrator application that we built for LotusLive. Social Network Integrator allows LotusLive users to share files with contacts from any of their social networks (LinkedIn, Salesforce, etc).

Underneath the covers, WaveMaker's Social Network Integrator application was hosted on Amazon EC2, using Rightscale for cloud scaling and Kapow to access contact data from LinkedIn.

Friday, January 16, 2009

Adobe Plays Catchup to WaveMaker...Again!

Savio Rodriguez has a nice post on the Infoworld blog, entitled Adobe follows WaveMaker's footsteps into the cloud, describing Adobe's latest cloud announcement as a reaction to the WaveMaker Cloud launch last December.

According to ZDNet's Larry Dignan, Adobe is launching a cloud version of their LiveCycle tools running on Amazon EC/2 as a "sandbox" for developers. In contrast, the WaveMaker Cloud development tools are intended for full application development and deployment - out of the sandbox and onto the beach!

WaveMaker is turning out to have much more of a lead in this space than we expected. When we started development almost 2 years ago, we assumed that there would be a number of open development tools targeting the cloud.

Now that we are well into our beta release, we are finding that WaveMaker is more unique than we had hoped for. All the major players who launched before us -, Coghead, Bungee - have gone down the old fashioned proprietary path.

For customers, this is a lock-in nightmare:
  1. Proprietary languages like Apex force developers to start fresh on yet another language and framework learning curve.

  2. Lack of portability across cloud providers forces companies to pay monopoly pricing to host on a single cloud.

  3. Lack of portability between the cloud and the data center limits the kind of applications companies are willing to put in the cloud.
The result is that any SaaS company that is looking for cloud-based development tools is looking at WaveMaker as a very attractive way to extend their platform. WaveMaker is an open and portable version of the tools that have helped make SalesForce the 500 pound gorilla of the SaaS world.

KANA was the first major software vendor to use WaveMaker as the customer-facing dev tool for their call center platform. Stay tuned for our next big partner announcement in the coming week!

Wednesday, January 07, 2009

Complexity Kills: SOA = CORBA 2.0 = DOA

Anne Thomas Manes of the Burton Group has declared the death of Service Oriented Architectures (SOA). Like CORBA before it, SOA was a vendor-driven "market" of daunting complexity. Also like CORBA before it, SOA collapsed under the weight of its own learning curve.

I attended the Gartner architecture conference last month, where 1,000 corporate architects gathered to discuss the state of SOA. The conversation was dominated by architects quizzing each other on what SOA really meant and whether any of them had really implemented it yet. That is scary for a technology that is long in the tooth from a buzz cycle perspective.

There was exactly 1 presentation I saw that presented a strong business case for the SOA architecture. That was by the CIO of National City Bank, which was recently bought by PNC and whose SOA architecture may or may not survive the acquisition.

Anne Thomas Manes also points out that while the heavyweight SOA architecture is falling out of favor, lightweight architectures based on SaaS and cloud services are on the rise. WaveMaker and other platform as a service (PaaS) vendors are delivering increased flexibility and productivity without the huge upfront investment of SOA.

Here is why SOA died and how the more flexible cloud services approach is winning:
  1. SOA blew the elevator pitch. Just explaining what SOA is takes longer than the average business manager's attention span. Like spinach, business sponsors are assured that SOA is "good for you." In contrast, the value of building cloud-based apps that work like Facebook and iGoogle is easy to convey, because business sponsors (or their kids) use useful web apps all the time.
  2. SOA was more about vendor enrichment than customer enrichment. I would argue that the SOA market was driven by the need for application server vendors to find add-on products that they could charge for once JBoss and Spring took the money out of the core app server market. In contrast, cloud services are growing organically as companies like SalesForce and WaveMaker make cloud development tools available that enable architects to build business applications based on best practices drawn from successful consumer sites like gmail and facebook.
  3. SOA swims against the tide of IT democratization. In retrospect, many companies that adopted SOA did so as a way for core IT to maintain control over every single computing event that occurs within an enterprise. In contrast, SaaS and cloud computing break the IT monopoly on compute cycles and deliver compelling cost and time to market benefits to the business.
Just as with CORBA, SOA introduced some useful concepts around enterprise integration and service reuse. However, just as Web 1.0 killed CORBA by introducing a much easier way to distribute applications, Web 2.0 has killed SOA with a much easier way to integrate web services.