Defining Enterprise Mashups
A few weeks ago JackBe’s CEO and Co-Founder, Luis Derechin, had the opportunity to represent the Web 2.0 industry on a major television network. When mainstream media outlets like Fox Business News start giving your product and your industry primetime coverage, you know you've passed a milestone.
During the interview, Luis was asked to describe ‘what that is’ and to give a ‘mainstream example’. Now I am not here to critique my boss (I am not that foolhardy). But I will tell you that Luis thinks he could have done a better job of defining enterprise mashups in a meaningful way for the uninitiated, non-technical business audience. So the boss asked his team to noodle it and that’s the topic I am interested in discussing here. How do you define ‘enteprise mashup’?
The simple word ‘mashup’ is complicated enough. You’d think with all the media and analyst coverage that there would be a simple, unified definition. Sadly, you’d be wrong on that one.
There are almost as many uses of the word ‘mashup’ as there are experts. And the term is all too common outside the high-tech industry as well. It’s popular in the world of music remix (this is where the word originated, in fact) but I’ve also seen it used by everyone from Sports Illustrated to the coupon-clipping Mashup Mom. I’ve even seen the word used on the back of a children's cereal box.
And it gets more complicated once you add the word ‘enterprise’ to the mix. When defining the enteprise mashups, it just doesn’t seem sufficient to say that ‘it’s a mashup in the enterprise’. A self-referential definition like that only seems to lead to more questions. It’d be more useful to have a self-supporting definition, I think.
Almost 2 years ago we went to great lengths to define a mashup. Today, with 2 years of enterprise mashup implementation experience behind us, we often say that enterprise mashups are:
‘Dynamic web-based applications that combine multiple data sources in real-time for increased awareness and improved decision-making while meeting the stringent governance and data security requirements of enterprises.’Not bad, I think. But we need something a bit sexier for the next time we end up on TV. Remember, our goal is to craft something for the non-techy, the non-insider, the uninitiated. In a recent Twitter conversation with Web 2.0 Strategist Dion Hinchcliffe I gave him the 140-character definition: ‘Web 2.0 meets Excel’. His reply: ‘Now define Web 2.0’. Fair enough, we gotta find a definition that is not just for the insiders.
How about defining enterprise mashups by example? JackBe has no shortage of ‘Mashups in Action’, including projects in government (the Defense Intelligence Agency), publishing (Thomson Reuters), shipping/logistics (Inttra), and banking (Accival), to name a few. But I’d hate to use any single example for fear of having the listener pigeonhole enteprise mashups into one or two industries.
We could define mashups by exclusion. For instance, mashups are not ESBs, BI, portals or fancy spreadsheets. Enterprise mashups complement all of these technologies, certainly, but they have distinct qualities from these technologies that set them apart. Unfortunately for our purposes today, I think the list of 'nots' is too long and cumbersome to be a useful defining tool.
Last, there is the always the ‘do nothing’ option. In other words, we could use the now-famous (but somewhat paraphrased) quote from late Supreme Court Justice Potter Stewart, ‘I can't define it, but I know it when I see it!’.
Somehow I don’t think my boss would think of this last as my best effort. So, let me punt it to you… How do you define an enterprise mashup?
-----------
Update 03-12-2009: We've had so many great responses to this topic that we started a 'Beat the CEO' contest on our Mashup Community: http://www.jackbe.com/enterprise-mashup/blog/announcing-beat-ceo-contest. Define 'enterprise mashups' for the beginner. Our weekly favorites get a $50 Amazon gift card and the honorary title of 'Mashup CEO'.



11 comments:
My definition for the lay person: "mixing business software components together to create new useful functionalities". The only difference between enterprise mashup vs. good o' regular software mashup is that it is business software components we're mixing.
Ed, I like your suggestion but I think 'business software components' still doesn't put things into non-techy terms. I also think your definition sounds a bit like the old definition of 'composite applications', which means the definition doesn't really highlight those qualities of enterprise mashups that make them special. Keep at it!
My distinction for an enterprise mashup is that it combines data from different sources that weren't previously combined. I think for a mashup to be useful in an enterprise it needs to be in data form so it can be analyzed, charted, and shared. So this excludes the web screen scraping mashups, for instance.
For anyone interested in more on this topic, I wrote a whitepaper on mashups and the business case for enabling enterprise end-users to create them at http://www.inetsoft.com/resources/prDM/evaluate/whitepapers/
Mike, your paper is great! I particularly like the 'Fallacy' section. And I do agree that mashups are data-centric solutions that make data accessible, visible, & understandable. But I think your section on defining mashups is a bit long (much like my CEO's version was). Can the 1st page of your paper be distilled down to a soundbite? Or am I on a quest that has no possible happy ending?
I am not sure about the exact definition of mashup. If I receive data from many services through SOAP, REST or whatever, assimilate and possibly message them all on my server and then present it to the browser, is it a mashup? Or is it necessary to collect and blend data only on the browser through java script, AJAX to qualify as a mashup? Or maybe the techniques don't matter.
Pranab, you should check out http://www.jackbe.com/enterprise-mashup/forum/beat-ceo-contest. We've got some great community-contributed definitions of enterprise mashups there. And I agree with you that the fundamental function of a mashup is, as you say, to 'receive data from many services through SOAP, REST or whatever, assimilate and possibly message them all on my server and then present it to the browser'.
I do think the techniques used to create mashups matter a great deal. For example, I don't think that 'blending' at the browser is appropriate for most enterprises. It opens up security issues and limits the sources of data of the mashups. Browser-based mashups also doesn't lend themselves to reuse and collaboration with other mashup creators. Server-based mashups avoid all these pitfalls.
a Mashup is a tool that understands unrelated web pages, software and data from many different places that will actually revolutionize the way you work and the way you integrate knowledge and processess for the creation of new things.
a Mashup is a tool that understands unrelated web pages, software and data from many different places that will actually revolutionize the way you work and the way you integrate knowledge and processess for the creation of new things.
a Mashup is a tool that understands unrelated web pages, software and data from many different places that will actually revolutionize the way you work and the way you integrate knowledge and processess for the creation of new things.
I am a new learner to this field of enterprise mashup. From a non-techie perspective, I would say: Enterprise Mashup is... the concept and supporting solutions of weaving together of information that facilitates users (such as businesses, suppliers, regulators, and end-consumers) to carry out their roles better, simpler, in a time and cost-effective manner, and achieving greater satisfaction.
Chris, we should be able to mashup the mashup definitions by now :-)
Post a Comment