Ross Mason gives a talk on Enterprise Mashups. 5 years ago mapping mashups were 35% of mashups and generally, they comprised of REST, RSS, Email, Web, XML, DB and JSON. Enterprise mashups are more data centric and involve much more robust policy-based security. It usually adds, MS Office, Files, PDFs, CSV and other e-Mashups.
The long tail problem: IT focuses on 20% of problems that affect 80% of users, whereas e-Mashups can focus on the rest. It’s hard to generate a use case around them because they tend to be more departmental or situational. So far, mashups have failed in the enterprise for the following reasons:
- Hard to define because they tend to be transient and situational
- Aimed at users and not developers
- No single value prop
- Difficult to sell to the business
- Tens of mashup platforms went out of business
Brighter future for mashups because 88% (based on his survey) need to integrate with other apps quickly. Other considerations are wealth of public APIs, evolution of SOA in the enterprise, and wealth of RAD frameworks (GWT, ExtJS, Grails, etc.).
Users don’t typically build software so it has to transition back to developers to building mashups on a mashup platform. This is required to put the right services in place to realize the end mashup GUI. e-Mashups are a natural extension of SOA to provide information to the end user more quickly.
Patterns for Mashups
Michael Ogrinz is writing a book on e-Mashups. He breaks the patterns into for groups: harvest, enhance, assemble and manage data. Feed Factory aggregates multiple feeds into a single feed. Super search searches DBs, filesystems, Data APIs, etc. into an aggregated search. Pipelines allows you to retrieve, process and create new data sets along the way.
For more information, check out the slides here.