Feeds

Betamax 2.0: the future of mashups?

Complexity gets complicated

Top 5 reasons to deploy VMware with Tegile

Simplicity in software is, I believe, more than just a noble aim; it is essential for successful software projects. However, simplicity should not be assumed just because one particular technology or methodology is being used.

Mashups, discussed recently by Reg Dev reader Aubry Thonon, are a case in point. One element of the hype around mashups is they are simple to build because all you have to do is link together a few APIs and then you are done.

Life is never that simple, though. Building successful, effective, reliable and long- running mashup applications is not a trivial task, and - indeed - is something that creates its own architectural, organizational and implementation problems.

The current, popular, definition of a mashup is of a web-based application that combines data from two or more sources, into a single integrated solution. The most widely cited example of this is the combination of geospatial data from, say, Google Maps, with information on local businesses taken from an online directory or another data source. The end result allows the user to search for, say, a local baker and be presented with a map showing their locations and a brief summary of the sort of products they supply.

A mashup, then, is merely a new kind of integrated solution, albeit one using the web that can be built by anyone with the knowledge and access to a browser! Simple, huh?

No. Mashup developers will encounter integration issues well known to the software and database worlds, for which there are still no off-the-shelf solutions.

Infact, things are going to be a little more complicated in the mashup world. For example, unlike traditional integration, the suppliers of the source data that's mashed up are often not involved in the project, and may never have designed their data to be used in that way. This will create problems as systems do not automatically collaborate with each other.

Here, then, is my list of some of the most fundamental issues:

Lack of a single standard or technology: ok, some might call this choice, but developers are working with Asynchronous JavaScript and XML (AJAX) on the client, server side Java, XML-based web services, Representational State Transfer (REST) and RSS/ATOM data feeds. In addition, screen-scraping techniques are used to extract information from web sites that do not provide a more easily accessible data source. AJAX alone has 210 different frameworks, each with their own technical strengths and weaknesses, never mind differing levels of community support that will determine which survive for the long term and are really worth backing.

Complexity of architecture: combining multiple technologies, development styles and integration points in a single application does not a simple solution make. Indeed, while it is certainly possible to achieve a functioning system, the end result may well resemble a spaghetti of code using a pallet of interfaces and frameworks, rather than a cleanly engineered solution that's simple to use or to maintain.

Choosing a cloud hosting partner with confidence

More from The Register

next story
Preview redux: Microsoft ships new Windows 10 build with 7,000 changes
Latest bleeding-edge bits borrow Action Center from Windows Phone
Google opens Inbox – email for people too thick to handle email
Print this article out and give it to someone tech-y if you get stuck
Microsoft promises Windows 10 will mean two-factor auth for all
Sneak peek at security features Redmond's baking into new OS
FTDI yanks chip-bricking driver from Windows Update, vows to fight on
Next driver to battle fake chips with 'non-invasive' methods
UNIX greybeards threaten Debian fork over systemd plan
'Veteran Unix Admins' fear desktop emphasis is betraying open source
Entity Framework goes 'code first' as Microsoft pulls visual design tool
Visual Studio database diagramming's out the window
Google+ goes TITSUP. But WHO knew? How long? Anyone ... Hello ...
Wobbly Gmail, Contacts, Calendar on the other hand ...
prev story

Whitepapers

Why cloud backup?
Combining the latest advancements in disk-based backup with secure, integrated, cloud technologies offer organizations fast and assured recovery of their critical enterprise data.
A strategic approach to identity relationship management
ForgeRock commissioned Forrester to evaluate companies’ IAM practices and requirements when it comes to customer-facing scenarios versus employee-facing ones.
Security for virtualized datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.
Reg Reader Research: SaaS based Email and Office Productivity Tools
Read this Reg reader report which provides advice and guidance for SMBs towards the use of SaaS based email and Office productivity tools.
New hybrid storage solutions
Tackling data challenges through emerging hybrid storage solutions that enable optimum database performance whilst managing costs and increasingly large data stores.