Web 2.0 Mashups Almost Ready For Enterprise

Dion Hinchcliffe, in a blog post over at ZDNet, talks about the increasing business value of 'Mashup' projects. Some of these, he believes, may soon or already be ready for use in an enterprise environment. He demonstrates one of these upcoming projects, showing off IBM's QEDWiki in a Flash demonstration. The software allows users to create their own mashups from canned widgets, turning data into simple applications with fairly straightforward functionality. From the article: "The motivations for mashups are quite different inside of organizations, where application backlogs and demand for more software that will improve collaboration and productivity are often rampant. If this state of affairs is true, far from having too much software, most enterprises don't have enough to satisfy demand, despite the prevalence of mountains of existing enterprise systems, many of which are underutilized. The arguments for letting users self-service themselves with end-user application tools and getting IT out of the critical path for the backlog of simpler applications are extensive." How important do you think 'self-made' software will be in the future?

Comments

welcome to the 90's, 80's

[yagu]

I'm not going to ax for extra credit or anything but, I wrote mashups in the 80's. FTA:

In decades past, the new ideas in computing originated in the enterprise world and trickled down to the consumer world later on (things like databases, computer networks, file servers, and so on). However in the Web 2.0 era, for reasons too complex to go into here, new ideas and approaches are germinating more on the consumer Web than from the enterprise space.

I would claim this specific notion (mashups) not only originated from the enterprise and trickled into internet consciousness, enterprise "mashups" existed many years ago. I know, I wrote them. It was (or at least we called it) surround technology.

We took vital pieces of different applications and wrote wrappers which allowed users with very simple interfaces to access more data more accurately more quickly. One example was a service order writing routine for small business that routinely took over 30 minutes... using our "mashup", we accessed the necessary enterprise applications and melded into a single app presentation and shortened the 30 minute process to less than 5.

I could go on, there were at least three other major applications we wrote (small team of 2, sometimes 3), that were "mashups". The advent of browser technology simply gave us another presentation tool, the notion and mechanics of mashing was still there.

I've played with Google "mashups", and Amazon "mashups", they're really nothing new.

There was a (don't know if they're still there) a Strategic Computing Consortium based in Boston, Ma, and they were huge advocates of surround technology and not only taught techniques and reasons for approaching solutions this way (I won't go into it -- it was a six-week class). And they provided and sold tools and consulting for putting these new applications together... the CEO (I believe) was John Donovan, author of a few college texts on OSes, and another major contributor was Stewart Madnick, one of the original authors of CMS (IBM's Conversational Monitoring System).

I'm won't claim they were the "founders" of mashups, but what they espoused and taught was mashup technology, and they were teaching it in 1986 (that's when I attended the consortium). The more things change, the more they stay the same.

(Also, as an aside, the article implies this new magic allows for "easy" creation of new applications. This is hardly so. All the care and due diligence of putting an application are still required. The effort can still be significant... There is certainly time saved if a team leverages existing critical applications but to toss this out as magical and easy for any end user community to leverage is probably glib and misleading.)