Friday, June 12, 2009

A Week in a Blink

It is never boring to work at a software company in an exploding software category. But this week the usual frenetic pace of the enterprise mashup market moved up an order of magnitude. If you blinked, you might have missed something juicy.

InfoWorld started the frenzy by publishing ‘Enterprise mashups gain traction at last’, an interview with John Crupi, JackBe’s CTO ‘Tech Titan’. And just yesterday, InfoWorld doubled down on enterprise mashups with a short op-ed piece from the intrepid David Linthicum, ‘JackBe is practicing safe mashups’. (You gotta love the title of this one.)

Anthony Bradley and David Gootzit at Gartner announced 3 new papers related to enterprise mashups: ‘Building a Business Case for Enterprise Mashups: A Gartner Framework’, ‘The Five Core Principles of Enterprise Mashups’ and an almost-published ‘A Gartner Reference Architecture for Enterprise Mashups’. (We’ll definitely be talking about these reports a lot more in future blogs.) And Anthony followed up his 3 publications with a detailed blog, ‘You Can’t Build a Business Case for Enterprise Mashups’.

And there’s more. Through a day-long series of Twitter tweets, the SD Times announced the winners of their annual ‘SD Times 100’ Award. The winners in their ‘Mashup’ category included JackBe, Serena and, a bit surprisingly, Tibco. We’re hoping the editors of the SD Times give us a bit of insight into the inclusion of Tibco when they publish the formal awards article on June 15.

Finally, I am happy to say that JackBe made it’s contribution to the week's enterprise mashup maelstrom. First, we released the Spring 2009 edition of our multi-award-winning enterprise mashup platform, Presto 2.7. And we simultaneously announced the Share Your Mashup Macro Contest.  You can grab the free Developer Edition of Presto 2.7 and participate in the Mashup Macro Contest on our Mashup Developer Community.

What more could ya want in just 4 days? After all this, I can’t wait to see what next week is gonna be like. Don’t blink.

Read More...

Tuesday, June 2, 2009

Smash the Silos, Mash the SOA, Share the Mashups…

This is my first ‘back-to-reality’ blog in a while. With so much talk about Web 2.0, social networking, visibility, accountability and transparency, lately it’s easy to lose sight of some of the practical day-to-day problems we have to constantly address. And if there is one persistent problem that won’t go away (and seems to be getting worse), it’s software “silos.”

In the physical world, silos are nicely contained structures that hold and protect things from the elements. There’s usually only a single way in and single way out. In software silos contain data we need but also make it difficult to get at.

Sadly, too much software ends up becoming a silo. That’s because requirements almost always revolve around solving a specific set of business problems at a specific point-in-time. Later, as the business grows and requirements change, we end up with a bunch of siloed systems that don’t talk to each other and most likely never will. In the end, we’re forced into the Excel-based manual mashup based on multiple systems of record and a copy/paste approach just to get basic-but-important answers from the data deluge.

But it isn’t hopeless. The Smash/Mash/Share approach is a quick way to build on your current architecture and do it in an agile, forward-thinking way.

Let’s start by examining the real nature of problem through a real-world example from one of my customers (who shall remain nameless). Let me know if any of this sound familiar:

I have a ten year old HR system that contains valuable information I use every day. Suddenly I have a new requirement to match my HR data with my sales forecast data (and related production resource needs) to get a picture of my future hiring needs.

I can’t get at the HR data without going through clunky, ten-year-old application client-server UIs. I’m forced to copy and paste the data into Excel. Similarly, my sales data is in our new custom Sales Automation system, which is only Browser based and has no export facility.

And once all my copying/pasting is done, I have copies of data that are already beginning to diverge from the systems-of-record they were copied from. Any real projections I put together are instantly suspect.


And if you think your warehouse/datamart, portal, or middleware systems will solve this problem, think again. In my experience, they have become simply more silos.

You’re going to have to look to newer Web 2.0 technologies that are built around agility and speed and don’t require months and years of required IT development. Even ‘America’s CIO’, Vivek Kundra has started looking to Web 2.0 solutions for answers.

Fortunately, IT has been using Service oriented architecture (SOA) as an architectural technique to expose silos as services. This doesn’t entirely fix the problem, of course, because only a Java/Flex/Visual Studio developer could consume a SOA WSDL. Now you just have silos with nicely standardized doors. But it's a step in the right direction.

That’s were mashups fit in. I like to think of SOA as silo smashers and Mashups as SOA mashers. Deepak Alur wrote a great blog that described “mashables” as services (like the aforementioned SOA WSDLs) that have been made mashup-ready.

Last, it wouldn’t be ‘Web 2.0’ if we didn’t enable easy sharing and collaboration. Lately it seems that everyone has agreed the best way for users to see and share data is via Widgets. (Of course, widgets that sit in front of mashups are better called ‘Mashlets’).

So there you have it: Silos are meant to be smashed. SOA is meant to be mashed. And Mashups are meant to shared. Like this:

The Smash/Mash/Share approach results in an agile platform from which users can solve unforseen problems in a agile, open way. This kind of information ecosystem lets people create and share in a way that can ultimately result in a powerful network effect.

Silos: 0, Smashers/Mashers/Sharers: 1 (and then some).

Read More...

Thursday, April 23, 2009

Mashups in Action: Connecting the Sales and Marketing Dots

A friend recently said I was the 'king of repurposing'. I am not entirely sure if he was referring to my about reuse as an important step in the Mashup lifecyle, or if he was was referring to my life-long quest to teach others how to reuse content (like this blog) whereever and whenever possible. Regardless, it reminded me to write this Mashup in Action blog.

As you might know, we have written a number of blogs about Mashups in Action over the last few years. A few of my favorites case studies include Thomson Reuters (part 1 and part 2), The Defense Intelligence Agency (DIA), and Accival.

But this Mashup In Action is special. It's MINE.

Like every good marketer, I want to help my sales guys find, nurture, and ultimately close deals. We use many media channels to do that and we have great metrics on the early parts of the process until the moment we hand the prospective customer over to the sale folks. Why? Because then we are focused on their problems, and our proposal to address them. We (sales and marketing collectively) often miss subsequent interactions our prospective buyer has with the marketing channels that got them interested in the first place.

I've seen this same disconnect occur in every organization I have ever worked for. So my mashup addresses this quintessential marketing-and-sales problem: matching prospects in the sales pipeline to their subsequent interactions with our marketing channels. Afterall, if you've got a deal in the pipeline, wouldn't you want to know that your prospective customer just visited your company's website? And what they looked at? And for how long?

Here's a recording of my Marketing-and-Sales Mashup given by JackBe's Deepak Alur on stage at the Web 2.0 Expo a few weeks back:



This mashup gives my sales folks some great intelligence on their sales prospects. It helps them understand what parts of the corporate website that individuals in the prospect company visited, what features/modules/functions they may have liked/disliked, and perhaps even what medium (video, print, blog, etc.) was the 'stickiest'. Equally important, it helps us marketing folks understand the real influence we are having (or not having) on sales prospects.

I know this kind of problem isn't universal. It is less prevalent in organizations that used highly-integrated all-in-solutions (like Eloqua, perhaps). But there always seems to be one more source of information you want to connect to the prospective customer. 'Just one more thing' is always on the lips of a good sales rep.

I love a good hypothetical demonstration as much as the next guy but nothing can match a real-world applications like these. Oh, and because of this, my sales guys love me. Now that is priceless.

Read More...

Monday, April 13, 2009

Spreadsheet data is dead; not live. Don’t try to Recover(y) it!

Whenever you copy data into spreadsheet you instantly render it 'dead'. In other words, you severed its connection to the source and in essence created copy of the real data. This may be fine if you’re doing historical analysis and trust that the data is valid. But it isn't fine if the data always changes and the source/timeliness of the data is as important as the data itself.

Here’s a great example: Recovery data. As part of the Recovery effort billions of dollars are flowing to the government agencies such as FDA, HUD, HHS, etc. These agencies get the money and distribute it. But they are also the ones responsible for reporting on the data internally, ‘upternally’ (a word I made up to denote reporting up the agency chain) and externally (to the public). Multiply all the agencies times the number of distributions times the frequency of data changes and all of a sudden the government has a major data problem.

Welcome to the ‘Decade of the Data’.

We know that this effort is being coordinated at www.recovery.gov and President Obama has appointed Vivek Kundra as Federal CIO. I’m a big Vivek fan and applaud his past efforts on data visibility work in the DC government. His zest for innovation and data transparency (such as Apps for Democracy) is inspiring in a public servant.

So like any good citizen, I went searching for the Recovery data and discovered all the weekly Excel Recovery reports. It’s great to see the data making it’s way to the public but I’m troubled by the notion of having this data put out as Excel. What happens when the data changes? Do I wait for the next spreadsheet that updates the prior spreadsheet’s data? It’s easy to see that this data is dynamic and ever-changing. Manual reconciliation just won’t do. Oh, since Excel is a manual process, mistakes in the data can easily make their way into the reports.

The problem is seductively simple: Spreadsheets are so ubiquitous and so easy to use we tend to use it for just as many wrong things as good things. Specifically, Excel is not the right tool to manage real-time data. Worse still, spreadsheet data is not governed, not secure and not easy to aggregate with lots of other spreadsheets. Excel fails to meet 3 of the ‘5Cs’ of enterprise mashups.

I think it is easy to define the exact characteristics we need for true Recovery data visibility across the entire government. And here’s why: when it comes to live data across multiple sources, the value in this data is not the individual set of numbers, but rather the ability to look at the data aggregated, sliced and diced, geographically transposed (i.e. on a map), temporally depicted (can you say timeline?), and any other way we need to see it right now. This means speed in creating and visualizing the data is just as important as access to the data.

And if you think spreadsheets, data warehouses or portals can do this, think again. My fellow blogger Chris Warner often talks about his 'Dead-and-Deadly Data Matrix’ that I think nicely lays out how other enterprise technologies fit into the ‘Live and Secure’ information management spectrum.


There’s really only one way to do this and that’s using enterprise mashup technology. Enterprise mashup platforms (EMPs) are built exactly for this purpose: to provide the fastest way to interact and visualize data from multiple disparate sources in real-time and safely. They do it in hours and days, not weeks, months or years. And EMPs plug directly into the authoritative data sources and provide the necessary security and governance to make the data available and visible internally and externally.

And true EMPs let you publish the mashups as REST/XML services as well as mashup widgets (we call them 'Mashlets') that can land in your 1.0 portal, 2.0 portals (like Netvibes and iGoogle), collaboration platforms (like Sharepoint and Jive), mobile devices (like the iPhone) and even back into Excel as a live data source.  And that’s exactly what users want.  They want to have the data and visualization where they work, not where we want them to work.

The ‘Decade of the Data’ is definitely here. Let’s just make sure we do it the right way.

Read More...

Monday, March 30, 2009

Mashing Oracle without Oracle

As an ex-Oracle guy of 5 years, I know that Oracle-bashing is an enticing pastime. As proof, consider how folks like Paul Greenberg and Dennis Howlett have recently taken Oracle to task for their general 'failure to innovate'. I am generally not one 'pile on' and I certainly do not wish Oracle any ill will (JackBe is a proud Oracle partner and, personally, some of my closest friends earn their livelihood there).


But I stumbled across Oracle's corporate blog site a few days ago and I must say that it truly surprised me when I couldn't find 'mashup' in their blog tag cloud. Sure, a few blogs mention the term, but there are precious few that give the topic any real attention.

Any dedicated Oracle-watcher knows that they have no product, or concise feature-set within an existing product, to enable the virtuous circle of mashups. Considering that Oracle is the leader in data-driven software and manufacturers much the data-creating, data-management and data-reporting products in the world, how can mashups NOT be on Oracle's radar?

Luckily, those who want to bring some mashup agility and efficiency into their organizations can get help from places other than Redwood Shores.  I recently put a camera in front of Danny Malks, JackBe's VP of Application Platform and got him to walk through the fundamental value of mashup for Oracle-driven enterprises. Here's his 3-minute walk-through of mashups for enterprises that use Oracle (a little or a lot):



And I can tell you that Danny's example is just the tip of the iceberg. JackBe's Chief Oracle Mechanic, Karthic Thope, recently showed off a killer 5-part mashup that included Oracle Siebel, Oracle Peoplesoft, and Oracle E-Business Suite, all secured through Oracle's LDAP and all of it delivered to Oracle WebCenter. You can check out the 15-minute demo at http://www.jackbe.com/videos/JackBe-MashupsForOracle.mov (be patient, it is a very big video).  This is, in my studied opinion, a true example of an enterprise mashup.

I know that some might say 'Oracle has that kind of stuff on its roadmap'. Perhaps. An organization of Oracle's size always has a lot of promise. But 'just wait' is no longer a workable reply and Oracle has a lot of things on its plate. I wrote about this simple quandry almost 18 months ago, asking 'how long do you wait while Oracle is executing on its massive product integration plans'?

And since that post, I think it is an understatement to say that our world has changed drastically. Now a 6- or 12-month delay can truly mean the difference between a company in the black and a company on the block. Organizations need to find a way to innovate in the fastest, most agile way today.

JackBe will be showing Oracle Mashups at Collaborate 09 in Orlando in May.  Stop by our booth.  We'd love to mash with you there. No waiting.

Read More...

Wednesday, March 25, 2009

The Sharepoint Dilemma

A recent ZDNet blog post from Dion Hinchcliffe entitled "Sharepoint and Enterprise 2.0: The good, the bad, and the ugly" discusses Microsoft SharePoint within the context of Web and Enterprise 2.0.

Frankly, outside the impressive adoption rates for SharePoint in corporate America today, the story ends up being mostly about the "bad and the ugly" from a feature perspective. SharePoint is good at some things and not so good at others, which is not unlike other products. When it comes to mashups, I think it falls somewhere in the bad-to-ugly area.

I think it is very important to realize, especially for an organization that is hoping to capitalize on SharePoint as part of their Web 2.0 initiatives, that Sharepoint's out-of-the box feature set simply does *not* support dynamic integration of disparate information sources, nor is it an open, cross-platform solution.

We think alot about Mashups and SharePoint here at JackBe. The dynamic integration capability of Enterprise Mashups is critical for leveraging SharePoint to its fullest. Not coincidentally, we are in the middle of a 10-part blog series on Mashups for Sharepoint that includes such topics as:

- SharePoint Mashups using standard SharePoint Web Parts
- SharePoint Mashups using Custom-built SharePoint Web Parts
- Using C# and ASP.NET UI Controls to build Mashup Applications in SharePoint

Presto, JackBe's Award Winning Enterprise Mashup Platform, lets you create mashups that are reusable within and across Microsoft and non-Microsoft environments, including reuse of the same mashups within SharePoint and your Enterprise Portal. These mashups are secure and governed, working within your company's access control and Single-Sign-On (SSO) infrastructure, and focus on user-driven solutions that support more rapid and more intelligent decision making.


SharePoint may not be the one-stop shop for your mashup needs but you can add enterprise-grade mashups safely and efficiently. You can try out Presto Mashups for SharePoint through our free Developer Edition from our Mashup Developer Community and be up and running immediately doing SharePoint mashups.

I encourage you to give Enterprise Mashups on SharePoint a try and let us know what you think! And if you'll be at SPTechCon (The SharePoint Technology Conference in Boston on June 22-24), stop by our booth for a demo and one-on-one tech-talk.

Read More...

Tuesday, March 10, 2009

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'.

Read More...

Wednesday, February 11, 2009

It Pays To Be Virtuous

We write about enterprise mashups on a fairly regular basis.  But we'll be the first to admit that we're not the only ones spending our nights and weekends noodling enterprise mashups.  The Mashup Tribe is a very big and VERY busy group!

Today we're very proud to have one of the Tribe as a guest blogger.  Mike Ogrinz is an enterprise architect at one of the largest banks in the world and, more important to our purposes, author of the upcoming book Mashup Patterns.

In the process of writing his book Mike has spent a lot of time considering enterprise mashup implementations, best practices, and theory.  In this post Mike takes a look at the 'virtuous' nature of mashups... 


I’d like to start this post by thanking the staff at JackBe for their support and encouragement while I worked on my book, Mashup Patterns (which will be available in March of this year). John Crupi, JackBe’s CTO and co-author of Core J2EE Patterns, had both the forethought to register MashupPatterns.com and the generosity to transfer it to me for my book’s companion site. I’m appreciative for the loan of this space to talk with you about what I think are some of the exciting aspects of mashups.

One interesting topic I explore in my book is something I like to call “The Virtuous Circle of Mashups”. It describes the process whereby mashups can be perpetually recycled and enhanced to build even more useful solutions:


Experienced software developers will look at this picture and think, “That’s almost the same basic cycle that we’ve been following since the idea of reusable code was invented. How is this different than re-using objects, component libraries, or third-party widgets?”

Under traditional reuse practices, there is no requirement that the consumers of reusable code are themselves reusable. So reuse is actually sort of a dead-end for the broader community. In my “day job” as an architect at a major financial services firm, I constantly come across commercial and open-source packages that liberally poach from the FOSS (Free and Open Source) world without giving anything back. This is where mashups break the mold. Mashups themselves are inherently reusable as the basis of new creations.

How many times have you used an application and thought, “It would be a great product if it only did this one other thing…”? Now imagine if you were empowered to make that enhancement yourself. And further, imagine when someone looks at your solution and can make the changes that make the solution perfect for them. This is a level of reuse and customization that is unheralded in the world of solutions delivery. Sure; I suppose you could make the claim that theoretically Open Source aims for the same goal. But did I mention that mashups also shift the focus away from IT personnel and closer towards end-users?

The rallying cry around application architecture has been “separate your business logic from your presentation logic” for a few years now. The idea was to keep the code that implemented business rules from getting mixed up with the code for creating the user interface. But the problem with this model is that both of these assets still remained locked within IT. The evolution of this idea is to give control of the business logic to the people who know it the best: business users! Mashup products like JackBe’s Presto are making this possible by enabling power-users to create their own products.

As exciting as this is, it’s only half of the solution. Empowering everyone within your firm to build their own solutions can have tremendous benefits, but also a number of dangerous consequences. I have seen end-users create Excel-powered solutions that sidestepped all of the best practices IT has painstakingly developed over the years. New versions are passed (and changed) from one user to another with little or no regression testing or auditing. Often, the same solution will be implemented many times over as coworkers re-work the same problems (unaware that a solution already exists). For mashups to succeed in the enterprise, they can’t just accelerate the mistakes of the past.

I believe that one answer to this dilemma is a centralized mashup “hub” or “repository”, where the community of builders can share, tag, and rate one another’s solutions. These “folksonomies” are a hallmark of Web 2.0 and lend themselves to brining a natural order to the decentralized development mashups enable. If traditional software reuse focused on the economies of scale, then mashups focus on the economies of collaboration. A central hub will give your enterprise mashup environment some of the advantages of Crowdsourcing, even if two employees never work on the same solution. The benefit of cooperative tagging and rating activity helps ensure that only the best (quickest, most stable, etc) solutions are remixed as the basis for new ones. You can even mix your internal components with an external repository (for example, programmableweb.com’s API-enabled mashup catalog).

JackBe's Presto Mashup Hub (click to enlarge)

Naturally, there are other critical product features and capabilities that firms will have to evaluate as they investigate this space. But in order to reap the benefits of The Virtuous Circle of Mashups, some type of community solution-sharing environment is critical.

We're flattered Mike has let us publish his thoughts.  We hope and expect he'll be back in the future with more!  Until then you can find more posts from Mike on mashups and mashup patterns at MashupPatterns.com.

Read More...

Tuesday, January 27, 2009

Government 2.0 is here. Are you ready to participate?

When the maverick CTO of the District of Columbia, Vivek Kundra, announced the Apps for Democracy  contest, I was intrigued for 2 relatively disconnected reasons.  Personally, I cared because this was a great example of an innovative government that could truly impact me on a personal level.  Better roads, better transit options, and better social services are all things I would appreciate in the place I have called home for the last 18 years.

But I had a slightly less selfish interest as well.  ‘Open government’ was something that I had spent 2 decades helping nurture and I suddenly saw Mr. Kundra's Contest as part of a broad trend towards 'Government 2.0', where service to the citizen is made better through dynamic, adaptive '2.0' technologies.

This is why I am about to break one of my oldest, most definitive personal rules. The rule? As a long-time DC area resident, I try very, very hard not discuss politics or government (or the Redskins). This is such a politically-charged atmosphere that I always seem to find myself on the wrong end of the conversation.  But I think it’s time to break my rule. Because I think ‘Government 2.0’ is here, in a big-and-nationwide kind of way, and I am eager to see it flourish.

For those who might have missed it, Apps for Democracy was a textbook example of a government entity putting ’2.0’ stuff to work in ways that would benefit the taxpayer.  Using services from the District of Columbia 'Data Catalog', participants were asked to submit web-driven applications that used 'real-time data from multiple agencies to citizens — a catalyst ensuring agencies operate as more responsive, better performing organizations'.  What parts of Web 2.0?  Standards-based information services.  Community-driven application development. Ajax. Mashups. Mobile computing.  Even a diehard skeptic would have to admit that the variety of applications submitted to the contest  (JackBe submitted a 'Carpool Matchmaker Mashup') shows that there is a great deal of potential in the idea of applying 2.0 to government.

And DC is not alone.  Seattle recently launched an interactive ‘2.0’ citizen portal.  There are some cool government-driven mashups  in development for big agencies like Housing and Urban Development (HUD) and the California Health Care Foundation (CHCF).   And there are great regional and local 2.0-style government apps of note like the 'City of San Francisco Bridge Preventative Maintenance Program Web Application', 'City of San Mateo Master Address Database', and the 'City of Boston Redevelopment Authority: Web Based GIS Redevelopment Project Tracking Portal', among others.

Of course, as a mashup vendor JackBe is doing our part as well.  Our work with the Defense Intelligence Agency (DIA) on ‘Overwatch’ is entering it’s third year.  Overwatch is one of the earliest mashups in government and the success of this early mashup project has inspired other mashup efforts such as the NSLDSS project by the Defense Information Systems Agency (DISA) on behalf of the Joint Chief of Staff.  And we’ve got mashup-driven efforts underway with a number of other government entities.

Considering the pressures we face as a nation, these efforts come none too soon.  A recent Wall Street Journal article noted that ‘…an [intelligence] analyst's query might scan only 5% of the total intelligence data in the U.S. government…’.  That’s hardly the broad perspective you’d hope for and I expect the capability is even grimmer in government agencies that don’t have ‘intelligence analysis’ in their mission statement.  It’s time every agency in charge of regulating or analyzing an industry or geopolitical situation make data access, information-driven insight, and true situational analysis a core competency.

Luckily, it appears that this service-through-innovation thing is going to have the support of 'upper management'.  Obama the Candidate made good use of technology in his campaign.  And with no apparent pause at all, the new media team of President Obama outlined three top priorities of the new presidential administration – communication, transparency and participation – on their very first day.  We have a newly-defined ‘National Chief Technology Officer’ (and one of the leading candidates for this position is none other than Vivek Kundra).  It even appears that President Obama is making a individual contribution to the cause by bringing a Blackberry with him into the Oval office.

Is Government 2.0 really here?  Government certainly 2.0 seems to be on the agenda for the next 4 years.  Heck, there's already a 'Government 2.0 Camp' and someone's already designed a Gov 2.0 t-shirt! So perhaps the real question is this: if Government 2.0 is here, how are you going to take part?

Read More...

Monday, January 12, 2009

Do You Know the 34 Mashup Patterns?

The folks at Programmable Web recently posted an interview with Mike Ogrinz, author of the upcoming Mashup Patterns book. His book will certainly help organizations understand the importance and possible applications of mashups in an enterprise setting.

The majority of Mashup Patterns is dedicated to describing 34 patterns grouped into five main categories. Every pattern includes case examples, a 'Fragility' rating, and a mapping to a 'Core' set of mashup abilities. Here at JackBe we live and breathe many of these patterns every day.

Mike concludes his book with some real-world case studies. JackBe is extremely proud that 2 of it's most interesting customer mashup implementations, the Defense Intelligence Agency and Thomson Reuters, are a part of this case study collection.

If you are looking into Enterprise Mashups, you'll want to learn more about mashup patterns. I'd propose a simple 2-step plan. First, buy the book (Amazon has it). Second, register for a live webcast with Mike as special guest on March 18. He is a great speaker and it will definitely be an entertaining and educational hour.

Read More...

Wednesday, January 7, 2009

Web 2.0 in 2009: What's Out, What's In

As a CTO, my boss tells me I am entrusted with ‘understanding market forces and business drivers to drive JackBe's technical vision and strategy’. So I am prone to trend-watching and predictions. In fact, I like predictions. And I think my 'Web 2.0 in 2008: What's Out, What's In' predictions were fairly good.

I should note that I think the end of the year is a fairly arbitrary time to consider ‘what’s next, what’s hot, and what’s dead-on-arrival’. After all, the Web 2.0 world changes everyday! Nonetheless, since it is what the rest of the world seems to expect, here’s what this '2.0 CTO' sees as OUT and IN for 2009:

Out: "Faster, Better, Cheaper", In: "Cheaper, Agile, Faster" (in that order)

Who doesn’t want “Faster, Better, Cheaper”. Well, it turns out, better isn’t always better, if the cost of improvement is high and the starting point is already good enough. Replacing “better” with “agile” and making “cheaper” the top-most priority certainly fits the economic climate. Managers want cheaper. And users want the flexibility to do things themselves and share it with others. And everyone wants faster. "Cheaper, Agile, Faster" seems like a no-brainer.

Out: Business Analysts, In: Mashup Analyst

With sincere apologies to those who have the title, what the heck is a 'business analyst' anyway? I know theoretically it’s a person who knows how to talk to the business and IT. But every year we induct more of the technically savvy straight into the business ranks. Many '2.0' technologies (like mashups, wikis, blogs, and some RIA widgets) are mature enough to let users create and share their creations themselves. So we'll start to see more titles like 'Mashup Analyst', 'RIA Specialist' and 'Wiki Manager' in the future.

Out: SOA by IT for IT, In: SOA by IT for the Business

SOA in the past has traditionally been done to 'reduce cost, increase reusability and provide standards based middleware for IT's use'. Because data is so valuable to the business, IT is now being driven by the business to make it’s SOA directly available to them. And it’s not just a nice-to-have, it’s a priority.

Out: Service-Oriented Data, In: Decision-Oriented Data

This is related (but not the same) as my 'SOA by IT for the Business' prediction above. SOA-enabled systems exchange data but because SOA has traditionally been created by IT for IT, SOA data hasn’t always been business (decision) centric. In other words, many SOA services do not exchange data that is human readable and more importantly in a state where users can use it for decisions. 2009 is the year that all changes. Following the path of consumer facing SOA services such as Amazon, Google and eBay, enterprise SOA systems will exchange data directly to (and from) the user or they will be passed over for systems that do.

Out: Better Business Intelligence, In: Lesser Business Intelligence

Business Intelligence made it on to Gartner’s Top 10 Strategic IT Technologies for 2009. I suspect that it isn’t BI in it’s traditional software sense that was the driver, but rather the strategic, enterprise-wide use of BI data. To gain more traction, BI will have to take more of a self-serve model rather than relying on IT do do it all. There are lots of things that are driving the 'BI 2.0' engine, including RIA widgets and mashups that use BI systems as data sources. It's a bold new world for BI, I think.

Out: SOA, In: SOA

We just can’t seem to shake SOA. We’ve been talking about SOA for almost a decade and for all intents and purposes we’ve been saying the same thing. But I expect that in 2009 that will change. Instead of talking about SOA as a tangible thing, we’ll talk about it as the only viable way to connect systems togeter and provide data to the business. Perhaps we'll go so far as to banish 'SOA' as a term and stick to 'service-enablement'.

Out: SOA-in-house, In: SOA-on-the-cloud

How many times do we hear “what are our sizing requirements for our SOA?”. The answer was always “it depends”, which resulted in weeks or months of analysis of hypothetical scenarios. The new answer will be “who cares, it’s on the cloud”. Seriously, all this sizing and planning is becoming so much less of an issue if the startup and operational costs of running more is so small. It costs more to analyze than to add another CPU or instance of Amazon's EC2! Who knows, maybe Amazon and Nike will team up on a joint marketing campaign called “Just Do It (on the Cloud)”. If so, I want credit for the idea.

Out: Dashboards, In: Mashboards

I think one of the underappreciated trends of 2008 was the dashboard. Every software vendors seemed to produce some sort of dashboard. But most of these dashboards were just fancy looking windows or portals into a single application. In 2009, we’ll see the same trend expand, moving beyond data coming from a single system. The result will be mashed up from multiple systems into what I often refer to as “mashboards”.

Out: Emailing Excel Spreadsheets, In: Mashing Excel Data

(This is a derivative of one of my 2008 predictions.) I would categorize data collaboration by emailing Excel spreadsheets as most successful software failure in the last twenty years. Imagine the billions of dollars spent copying and pasting data into Excel, manipulating the already-out-of-synch data, emailing them, and then re-assembling this information because it’s the only tool available to business users. I love that Google Docs is slowly hacking away at the sharing and collaboration aspect of this problem, but Docs are disconnected from the original data sources. Mashups tied directly to the data sources (this includes both Excel-bound data as well as primary databases/applications) can tackle this problem at the data source, and do it in a secure, governed way.

Out: Silo Bashing, In: Silo Loving

There is nothing pleasant about the term “silo.” It portrays images of things being locked up, impenetrable and self-contained. Sure, we can continue to provide proprietary hooks to our most valuable resource but it remains an expensive, unscalable approach. In 2009 I think we embrace our silos and learn to treat them as fact of life. In what way? SOA becomes the secret sauce that wraps these silos in a non-proprietary, standards-based access mechanism. This let’s silos become “mashable” and participate in the mixing and syndication with other disparate data sources. Long live the silo.

Out: Aligning Business and IT, In: Buying IT

If I read another whitepaper this year that talks about aligning business and IT, I think I'll throw in the towel and go into the wine business. Aligning Business and IT is a best practice that has been talked about for years now. If your business and IT are still not aligned, it probably ain't gonna happen in these tough times. So, it's time for drastic measures: Buy IT. Let IT do what it does well (secure and govern datacenter resources), while you (the business) buy (or lease/rent) your own mini IT group that builds your applications and mashups. This is what is often termed 'Shadow IT'. A corollary to this idea is buying your IT from outside the organization, aka SaaS. Either way, you'll get what you pay for.

Out: SOA Architects, In: SOA Social Workers

All software developers wanted to have “SOA Architect” on their resume at one time or another. But SOA has a very bad rep nowadays. There are many reasons why, but most of the reasons aren’t technical; they’re in fact social and organizational problems. Face it, most organizations have tons of 'data fiefdoms' and few of them are incented to share. Introduce the requirements to expose and share your SOA data outside of the firewall and across domains, and you’ve just exponentially increased your problem. But 2009 is the year that this all changes. I think a new breed of technologist (let's call them 'SOA Social Workers') will understand the technology and business but, more importantly, know how to work the politics.

Out: Salesforce.com as a SaaS, In: Salesforce.com as a Business Portal

How do you get your Salesforce.com users to have access to data inside your datacenter? The obvious way is to push your data into Salesforce.com. This might work for small data sets, but not for all the stuff that lives inside our monolithic apps like SAP, Oracle and Portals. In 2009 we will see companies beginning to dump their internal portals (because of IT budget cuts) and adopting Salesforce.com as their Business Portal. However, instead of uploading everything to Salesforce.com, they will be using RIA widgets to syndicate/embed their internal data/content to Salesforce.com. That's a savvy 2.0 approach.

Read More...

Wednesday, December 31, 2008

When Looking for Answers...Follow the Money

"Follow the money" is a common way experts rationalize human behaviors in economics, politics, crime and many other areas. This undeniable truth becomes even more relevant in an economic environment characterized by gloom and pessimism, such as the one we are currently experiencing.

It is with this in mind that we are proud to announce that in the midst of one of the most difficult economic scenarios in history, JackBe received $5 Million in additional funding from its existing investors to expand our sales and marketing efforts.

I have been asked by many people “how did you manage this in today’s economic environment?” Well, let's follow the money to figure out the reasons why…

The first clue in the money trail is based on the great promise Mashups have for making business cheaper and faster. With budgets tighter than ever, many organizations are turning to Mashups as a way to do more while spending less. Anthony Bradley at Gartner stated it very well in a recent blog post:


“…mashups may be one of the areas of innovation that continues to do well through the economic downturn. This makes sense as organizations looking to save dollars may look to mashups for a quicker and cheaper approach to integration and new app development.”

The second clue in the money trail is that JackBe has passed many notable milestones in 2008 as well: a ‘Best Enterprise Mashup Platform’ award, a major product release, a community for Mashup Developers, a free Developer Edition, and what we’d like to think is some industry-advancing thought leadership with some great partners.

However, nothing is more important than having new customers and delivering real benefits to them. Receiving the trust of enterprises who use the software we have created is the most vital clue in the proverbial “money trail”. It certainly confirms that there is much value and promise in what we do.

In my opinion, the money trail points out two notable facts. First, there is some tangible value to Mashup technology in the enterprise. But equally important, our customers are buying our software because of the fundamental shift in general enterprise technology from large-scale, monolithic efforts (ERP, CRM, custom applications and the like) to agile, dynamic projects that allow enterprises to take advantage of their existing infrastructure. And by doing so these organizations save time and money while achieving better operational business results.

I think that noted business author (and Member of the Mashup Tribe) Dan Woods summed it up nicely at a recent Mashup Camp:

"Mashups aren't doing things that are already being done by IT; they're doing things that users wanted but IT never got to. You won't get a new CRM system out of a mashup, but you will get a better CRM system that does things IT didn't have time to develop or know were needed."

As Dan noted in a column in Forbes, Mashups are being used by competitive enterprises to rapidly make improvement on their existing software ecosystems to add business value, without the lengthy and expensive projects of the past.

I think that by following the money trail of both investors and customers you can reach a simple but powerful conclusion: Mashups are good for business and they become even more valuable in a scenario where cost reductions and increased efficiencies are paramount.

You can bet that the trust from our investors, our customer's confidence, and the unique opportunity to make enterprises more efficient are the reasons that we will be working hard in 2009.

Mash on.

Read More...

Wednesday, December 17, 2008

My Predictions for 2009: Nothing

Every year I look forward to ‘the prediction season’.  You know it.  It’s that time of year when every expert, pundit, analyst and chatty blogger on the planet decides we need to hear their thoughts on the past year and what they think will happen in the coming year.

There are tons of examples.  I’ve seen predictions about SOA (David Linthicum in Infoworld and Joe McKendrick in ZDNet), IT spending/activity (CapGemini and ComputerWorld), Content Management (CMS Watch), Business Intelligence (Enterprise Systems Journal and Intelligent Enterprise), and of course Web 2.0 (Fast Company).  Gartner even has a Top 10 Strategic Technologies for 2009 where mashups made their list for the second straight year. 

I admit, even JackBe has played the soothsayer.  Our CTO, John Crupi, did a great job at the end of 2007 with his Web 2.0 predictions for 2008.  And I hope he does it again for 2009.  But I’ve decided to embrace my inner slacker.  I’m predicting nothing.  Literally.  Instead, I’m going to crowdsource the problem to my Mashup Tribe (that includes you).  Where do you think mashups will be in 12 months?

Of course I’m not a heartless taskmaster (in spite of what my son may say).  I have some great source material for you.  JackBe has spent the last 12 months talking with thousands of organizations and individuals about their perspective on mashups.  And we’ve collected their responses to one simple question: Describe the business problem(s) enterprise mashups will address for you.

And in true Web 2.0 style, I’ve published over 1000 responses to this question in a nice mashup widget (we call them ‘mashlets’), which you’ll find below. (On the off chance that your browser has problems loading the Mashlet inside this blog, you can access it directly.)

Loading Mashlet - MashupUseCases2008.Mashlet. Please wait...


Put on your thinking cap and take a look.  The widget has a nice filtering option (look for the 'Input' button), so try searching on common enterprise technologies like 'portal’, ‘soa’, and ‘dashboard’.  But keep an open mind as well.  I think you will be surprised at the broad range of responses.  There's even some funny ones in there.

Then give me your thoughts.  Where do you think mashups will be in 12 months?

Read More...

Thursday, December 11, 2008

Are You a Member of the Tribe?

I just listened to Seth’s Godin new book, Tribes: We Need You to Lead Us. Seth is an inspiring author/marketer and I find him to be one of the easiest-to-understand individuals about complex business topics today. His grasp and explanation of the complex problems facing organizations have made all of his books best sellers in the business world.

In his new book, Seth explains that Tribes are made-up of people who come together to support each other in endeavors in which they are passionate about.  He says it like this:
"A tribe is a group of people connected to one another, connected to a leader, and connected to an idea... A group needs only two things to be a tribe: a shared interest and a way to communicate."  (Page 1 of Tribes)
People who make-up a Tribe do not necessarily belong to the same company, social group nor are they located in the same geographic place.  In fact these individuals are not brought together by a single short-lived recruitment effort.  Instead, they have congregated together over time by pursuing similar and/or complementary interests and creating an informal network to exchange information with each other.  Seth goes on to say that PASSION is the thing that drives people to huddle with and find commonality with others.

In my case I am extremely passionate about Mashups in the Enterprise, like everyone here at JackBe.  How else would you explain our 5+ years of effort and the many challenges we have faced and overcome?  It is this passion that has helped bring us together from different backgrounds, leaving behind different comfortable jobs to jointly pursue the larger task of helping create a new category of enterprise software.

From this somewhat unique vantage point, we have seen and continue to witness the formation of a tribe of mashup supporters.  It is this group of pioneers who started talking about Mashups before they were called “Mashups”.  These people are the ones who found a way to combine information from widespread sources so that the combination means something to the end-user. 

These people are the ones that end up explaining what a mashup is time after time, explaining the differences between a Mashup and Business Intelligence or ESB.  It is this tribe of forward-thinking, innovative visionaries who have created a software category where others said none was necessary.

Seth also talks about using Web 2.0 tools to enable your tribe to communicate.  In our case, we have found that the Mashup Tribe requires a place where they can meet other tribe-members and exchange views on all things Mashup.   JackBe launched a Mashup Developer Community (MDC) a few weeks ago and we’re proud to say it has grown to almost a thousand members with members in dozens of countries including the USA, Brazil, Israel, Netherlands, Italy, France, Korea, Russia, Mexico, and India.  The one thing – the ONLY thing – that is common to all of these people is their passion for Mashups and their desire to see Mashups fulfill the potential they hold.

Like any tribe, ours has its more prominent members.  It is with great pride and pleasure that I can call out and recognize some of the “mashters” (mashup masters) of the Mashup tribe.  They all deserve recognition for their work.  Although I am sure, as Seth says in his book, few of them are in the tribe for the publicity:

Analysts and pundits like Anthony Bradley (Gartner), Oliver Young (Forrester), Dion Hinchcliffe (Web 2.0 strategist), David Linthicum (technology pundit, as he likes to say), Joe McKendrick (ZDNet, among other places), Lorraine Lawson (IT Business Edge), and the guys at Zapthink.

 

Thought leaders and authors like Larry Bowden, Dan Gisolfi, and David Boloker at IBM, Mike Ogrinz (author of the upcoming Mashup Patterns), Chris Thomas (Intel), Dan Woods (Evolved Media), Andy Mulholland (CapGemini and co-author of Mashup Corporations), Niall Cook (author of Enterprise 2.0), and Vince Casarez (Oracle).

 

Early adopters and supporters like Rich Barton (founder of Zillow), Brian Wilson and Tony Lucia at Thomson Reuters, Baltazar Rodríguez (Servicio de Administracion Tributaria), the organizers of Mashup Camp, Bob Gourley, Steve Willett, Bob Ware, and the rest of the Overwatch team at the DIA, Alejandro Vargas (Banamex Accival), Vivek Kundra (CTO of the District of Columbia), every submitter to the Apps for Democracy contest, Tim Hall and Marie-Paule Cellini-Odelier at HP, Abe Elias (Ext JS), Manuel Jasso (Wells Fargo), Mark Scrimshire (BCBS), Sean Kelley (Deutsche Bank), John Musser (Programmable Web), the guys in the CTO Office at EMC, Rigoberto Saenz (BBVA), the sharp-as-a-razor Kelly Shaw, and the organizers of the CSC Leading Edge Forum.


Of course I could never get to them all.  The tribe is just too large to mention everyone.  To the rest of you, and you know who you are, thank you.  It is a tribe I am very proud to be part of.

Finally, I’d like to mention that you can download the Tribes audio book for free here and “The Tribe Casebook” from Seth's blog.  If you are a reader instead of a listener, I’ll gladly send you a copy of Tribes (I have about 20 at my disposal); just send me a quick note at luis.derechin@jackbe.com.  I believe in the premises of the book and in my own tribe so much that I truly want to share them with everyone.

Read More...

Thursday, December 4, 2008

On Ed Yourdon Presents: Mashups!

I am big fan of Ed Yourdon. So I was delighted to see his presentation on Mashups (here). Discussion on this topic by eminent and experienced gurus like him are heart-warming and encouraging to me, since we at JackBe have been working in the area of Mashups to create a new kind of lite-middleware. I and my colleagues have often written about our work (for instance here and here).

What was not so encouraging to me personally was the fact that Presto, our enterprise mashup platform, did not figure in his presentation. Which got me thinking, no surprise really, there must be a whole lot of people that might not know or heard about us since we are such a small company compared to the likes of Google, Yahoo, IBM and Microsoft (which were featured mentions in his presentation).

So, to those of you who are not familiar with us, I would like to take this opportunity to introduce our company, JackBe and our product Presto, a pure-play enterprise mashup server platform built from the ground up for enterprise mashing!

At the core of Presto is our Enterprise Mashup Markup Language (EMML), which we describe as a domain-specific language (DSL) for mashups. No other product or technology offers such a DSL for mashing, which has been greatly appreciated by our users and customers. Do check it out yourself and let me know what you think.

We also offer Presto to developers in a special no-cost Developer Edition. Mashup Developer Community (MDC) members can download and use Presto for free here (requires registration).

In Ed Yourdon's presentation, he mentions Yahoo! Pipes, MS Popfly, etc.  I have heard some describe Presto as 'Yahoo! Pipes on steroids for the enterprise' since Presto's visual mashup composer (called Wires) allows you to create mashups that consume any kind of service / API including WSDL, REST, RSS, Atom, Databases, Excel spreadsheets and so forth. Pipes only deals with public RSS services as far as I know.

Presto also generates 'Mashlets', which puts a face (UI) in front of each mashup. Mashlets become the embeddable objects that can virally spread within and outside the enterprise (assuming the enteprise security policies allow them to share outside). All of this is done in a secure manner, which is why we are an enterprise mashup solution.

To better understand Presto at a high level, I had previously described the 3 artifacts of mashup process here. I hope this provides you some insight into our technology, and hopefully, you will get to try it when you get a chance. While doing so, if you do need any help, don't be shy to ask on MDC, the whole community is there to help!

Mash On!

Read More...

Wednesday, December 3, 2008

The 5 Most Common Mashup Mistakes

Mashups are a popular topic lately, in both IT and business circles. Gartner recently named them a ‘Top 10 IT Technology for 2009’. But if your organization is thinking about ‘getting mashy’, here are five common pitfalls that you can avoid with just a little education and forethought:

  • The ‘Fall for the Buzz’ Mistake: Misunderstanding what a ‘mashup’ is. Everyone wants to be associated with the hot buzzword and mashups are hot. Unfortunately, ‘mashup’ is a term that has also been used by vendors in areas like business process management, enterprise service bus (ESB), business intelligence (BI), and portals. So focus on the goal: mashups let you address just-in-time information needs by consuming and combining bite-size chunks of data, they run in ‘Internet time’ (i.e. seconds), they are usually relatively code-free, and they must make it easy to share with others. And there are, of course, a number of good independent software vendors that specialize in mashups.
  • The Self-Serve Mistake: Every few years we hear about tools that will turn users into developers. It ain’t true. Yes, users are becoming more technically savvy and self sufficient every day (we call them ‘Business User 2.0’). But we’ll need IT for a long time to come, acting it’s new role as ‘enabler’. In the case of mashups, IT will establish a secure, reliable, and robust mashup infrastructure through which end-users can get mashing. In non-technical terms, IT builds the mashup lab and the business gets to play mashup mad scientist without worrying about blowing up the building.

  • The SOA Mistake: Assuming you need an SOA before you adopt mashups. Sure, mashups put a business face on SOA, so to speak. And it’s easier for you to create mashups if there are a lot of ‘mashable’ (i.e. SOA-based) data sources. But the best mashup software can instantly turn databases and applications into mashable services.  So don’t wait for that 5-year SOA effort to be finished before you start the mashup rollout. Use mashups to help you define the optimal SOA.
  • The Silo Mistake: Mashups that aren’t reusable fall into the same ‘silo’ trap as legacy software. Mashups are their best when a community of like-minded users are building upon each other’s work. As we’ve written in the past, this kind of network effect does not happen automatically. Your mashup solution must have some kind of infrastructure to encourage reuse, such as a mashup ‘hub’, also often referred to as a ‘repository’ or ‘registry’. You (and your mashup software) have gotta have one.
  • The ”Oops” Mistake: Thinking about security as an afterthought. Mashups can be based on business-critical data from your ERP system, your SFA system, your CRM system, etc. And, once created, they are often sent to many destinations (think portals, iPhone, and spreadsheets). You don’t want to find out your data has been compromised just because you assumed some kind of security was in place, do you? Your mashup solution must let mashup creators choose who they share with and the permissions. And the entire continuum of mashup inputs to mashup destinations need to be incorporated into your mashup plan. In technical terms, you need mashups that include LDAP integration and single sign-on support so they play nicely in your secure enterprise.

Understanding these common pitfalls can help your first (and your 50th!) mashup efforts be successful. Ignoring them will likely lead to mashup misery. Now get mashing.

[Reposted from Fast Company.]

Read More...

Monday, November 24, 2008

Mashups can turn any Enterprise into a Superorganism

A few nights ago I watched a very interesting piece on the Discovery Channel about ant colonies called ‘Ant Wars’.  (Give me a few more lines and you’ll understand why this has anything to do with IT, enterprises or Mashups).  I was awe-struck with the way that an ant colony behaves as one unified being rather than millions of individuals - some ants perform one function, which other ants use to their advantage so as to be able to perform their function more easily, and so on, and so on. 

The commentator mentioned how scientists consider an ant colony to be a “Superorganism”.  The Wikipedia, as usual, had a helpful description of the term: ‘A superorganism is an organism consisting of many organisms…where division of labour is highly specialised and where individuals are not able to survive by themselves for extended periods of time’.  

Without much apparent centralized coordination and without any one individual leader barking-out precise orders to the individuals, each ant performs their own task in what appears to be a seamless orchestration of actions towards the achievement of a much larger purpose – that of survival of the colony.

As I have said many times, I see Mashups everywhere.  So I got to thinking that…

…with the adoption and use of mashup technologies, enterprises evolve into a kind of Superorganism where individuals create mashups to solve particular problems and by doing so create an environment of re-use where others can more easily solve subsequent, perhaps more complex, problems.

As the leading Mashup vendor, we are lucky to be a front-and-center witness to many cases where, with the use of our Presto Enterprise Mashup Platform, individuals in organizations are able to easily and economically take data from many different applications built by enterprise IT departments and mash it up with other services to solve their own problem. Then, those services are re-used and built upon by others to solve similar yet different problems.

This beautiful “ballet” of solution solving and application building happens with little planned coordination and appears to occur naturally without the central planning usually required. A Superorganism indeed.

Read More...

Thursday, November 13, 2008

Mashups : New and Agile way to Integrate

I came across this interesting post: How Mashups Could Eliminate Integration Projects by Loraine Lawson. In a related post, she refers to John Crupi's article Enterprise Mashups Part I: Bringing SOA to the People which I would recommend to readers who want to understand JackBe's take on defining mashups. Anyway, Loraine's post led me to Ron Schmelzer's ZapFlash. Here are some excerpts of Ron's article that caught my eye, with my take on them.

Excerpt from ZapFlash:

A year or two ago, assuming that a mashup was a web browser-based, static, user interface composition of web-based functionality would be a reasonable presumption. But in the enterprise context, none of those assumptions necessarily hold – we might want non-Web access to mashed applications, we might want to change them regularly, and we might want to mash up information that exists below the user interface abstraction. For sure, Web mashups might embody the ideals of the original mashup concept, but we now have the desire to mash up a wide variety of IT resources from application to infrastructure to data that might be exposed with a wide range of interfaces – or without. And, it’s the desire to mash up information freed from the application that diversifies the mashup term to include the concept of the data mashup.

Introducing the Mashup TierMy take: This hits the point right on what we at JackBe have been saying all along about mashups. While some mashups are done purely in the UI/Browser, in the enterprise, such mashups need to be supported by a new tier, the mashup tier, which sits between the presentation and business tier. So enterprise mashups will have some mashing done in the client, but most of the mashing happens in server side where security, governance, policies can be applied before any mashing can happen in the client.

Another excerpt from ZapFlash:

There are many scenarios for composing data, but some are better suited for static, tightly-coupled, IT-driven, non-Service Oriented form. In fact, 80% of the value that businesses derive from data come from the 20% of fixed, highly optimized data integration approaches implemented over decades. In this realm, traditional data integration approaches retain high value. However, it’s the other 80% of data integration requirements, most of which come from the need to meet short-term, often ad hoc, integration requests that cause 80% of the problems. Anyone who has lived long enough in the enterprise IT space knows that business-driven requests for reporting, forecasting, analysis, or other interpretations of data can present significant complications and cost to the IT organization. The reason for this is that the IT organization is set up to meet the recurring needs of the business and not “situational” needs for information.

Long Tail of Enterprise Software Demand My take: This highlights another issue which we have been talking about at JackBe about the long tail & enterprise applications need which was so nicely discussed here by Dion Hinchcliffe.

Bottom line: Something new and interesting is happening in the enterprise architecture space. A new flexible and agile tier is being introduced in the architecture to meet the increasing demand on IT and add value to existing architecture, applications, services and data. Question is, are you embracing this inevitable change? If not, it's still not too late. :-)

[Cross-posted from my personal blog]

Read More...

Monday, November 3, 2008

The 3 Parts of Mashing

Deepak Alur, JackBe’s VP of Engineering, has outdone himself. He recently posted a great blog on our Mashup Developer Community entitled ‘Mashables > Mashups > Shareables’. It does a great job of distilling a mashup down to 3 fundamental parts. You can post comments to Deepak in our Community.

How exactly does the mashup process work? What does Presto really do? These are a couple of common newbie questions. I have had different explanations for this, but of late, I have narrowed down on the following elevator pitch (trust me, this textual explanation looks long, but I can explain really fast in person) that I have used successfully with other developers recently. So I thought I will share this with the community in case it helps others to understand the process and artifacts around enterprise mashups.

I found it easier to explain the whole mashup workflow using three terms: "Mashables > Mashups > Shareables". (OK, I confess, these may not be in the English Dictionary yet.)

As a mashup developer or user, we need to start somewhere. To me that starting point is what I call Mashables. These are things that one can use, invoke to get data and send data. Things like services such as WSDL based web services, REST based web services, RSS or Atom services, proprietary XML/RPC services, or even the conventional RDBMS tables, view and stored procedures. I would also include other items such as spreadsheets, XML documents and unstructured information on internal and external websites. These are the raw material for mashups. These need to be made Mashable! And this is exactly what happens when you 'publish' one of these things to Presto. It becomes a Mashable artifact that can be normalized, secured and managed.

And then comes the second thing called Mashups. I don't want to go into a philosophical discussion about what a mashup is or isn't. However, I think mashup is a user-driven, user-focused thing that encapsulates the kind of data processing and manipulation actions a user would normally do to turn any data into real information. Such actions include joining, merging, sorting, filtering, constructing, transforming, clipping, and so forth. And in Presto, a mashup is represented by an small file written using EMML (EMML is Enterprise Mashup Markup Language). EMML is an XML-based dynamic declarative domain specific mashup language. Again, a Mashup becomes this artifact which can be secured and managed just like the Mashables.

The third and final thing is the Shareables. Once you have Mashables, and Mashups, you want to be able to share them with co-workers, partners, friends, whoever. Shareables can be exposed as a service interface so others can use it as a REST or RSS or Atom or WSDL service. Another popular type of Shareable is what we call Mashlets, which are enterprise widgets that offer a rich interface to the Mashups. Mashlets are not full blown applicaitons, but can be small micro-applications that encapsulate a very specific functionality. Mashlets can be shared by publishing them on Wiki pages, blogs, websites, portal servers. You can even email a mashlet or call it directly from a smart phone like iPhone. Other types of shareables include mashups and services shared as REST urls, RSS feeds, data feeds, spreadsheets, email and so on.

There you have it. Now I can just describe Presto simply as a platform to securely create, publish, consume and collaborate with Mashables, Mashups, and Shareables!

Read More...

Tuesday, October 28, 2008

Free Enterprise Mashup Software by the Developer, for the Developer

We've spent the last couple years at JackBe designing and building our enterprise mashup product from the ground up.  We’ve won some nice awards, introduced some genuine innovations (like our Enterprise Mashup markup Language, which just passed it's 1-year anniversary) and, most importantly, been blessed with some great customers


And now we’ve taken our 2+ years of hard work and made it available for free as the Presto Developer Edition and our Mashup Developer Community (which we lovingly refer to as 'the MDC').  We want all of you to take Presto for a spin and let us know your thoughts.


One notable developer who has given Presto a try is Steve Graham, Senior Technologist in the Office of the CTO at EMC.  He’s created an intriguing mashup that tackles some common issues in the datacenter.  And I think Steve’s perspective is representative of many long-tail business problems outside the datacenter as well. 

 

In his screencast of an enterprise mashup that supports IT/Data Center resource management, Steve points out that many problems in the data center require the synthesis of both modeled and non-modeled information.  Additionally, Steve discusses how these sorts of mashups require a server-centric approach to support the joining of disparate information sources with the desired level of security and performance.

 

I certainly agree with Steve’s technical assessment.  But he also underscores a broader point: organizations that have many systems will need solutions that can bring them together.  JackBe is happy that our new Presto Developer Edition provides an answer...and it's free!!!

Read More...

Friday, October 17, 2008

Mashup Recycling: Now this is Green IT!


Sometimes ideas come from the most unlikely of places. Yesterday I got off an elevator and wondered if it was one of the energy-saving models that regenerates power. They ‘give back’, in a sense, making the next round trip less costly than the previous one. An instant later I found myself noodling this very same principle in the world of mashups.

Mashups can be used to build new mashups. They make the next mashup easier to create. It this is the very quality that gives mashups the majority of their ROI and separates 'once-and-done' custom mashups from long-term systematic mashup solutions that achieve a kind of fission via a community of mashers. And in my considered opinion, mashup reuse is one of the most important yet under-utilized qualities of mashups. I think mashup reuse needs it’s day in the sun.

Enterprise mashups can be built on raw data sources (SQL databases, for example) and more formal services (like REST and WSDL). But mashups can also be built upon other mashups, assuming your mashup tool lets you publish the mashup with some sort of callable service interface. So more mashups mean more raw materials to go into the next mashup, creating a kind of network effort. You’d think this might be a no-brainer but I frequently see mashup implementations that that have no reuse at all.

Most mashup vendors show a mashup lifecyle as a circle; the last arrow that closes the circle is the 'reuse'. But this kind of network effect does not happen automatically. Much like the best SOAs, mashup reuse requires some kind of infrastructure to encourage reuse, such as a mashup hub/repository/registry.

Much like the worst SOAs, it is easy to forget about reuse and end up with a bunch of point solutions that stand alone (and miss a lot of the real ROI value of the technology). I see lots of cool mashups that are custom-coded in Java or Javascript. Most of these essentially become a 'mashup silo', with no option for reuse of that mashup's service in the next mashup, particularly for mashers makers other than the original creator.

But technology alone doesn't equal mashup reuse. A second common stumbling block is a social one. You need to change mashup making behavior. Sure, most enterprises have a common organizational mission but that doesn't imply that these same organizations motivate their employees to explicitly think in 'reuse' terms. There’s no magic bullet in any software package that will do that. Mashup reuse takes knowledgeable, committed leadership that can take independent-minded people and make them into a community of mashup makers that look for reusable mashup inputs and strive to create reusable mashup outputs.

Much like real recycling efforts, you need a pro-active, systematic, persistent ecosystem-wide commitment for real mashup reuse. Keep it green, baby.

Read More...

Monday, October 13, 2008

McKinsey Recommends Mashups for Managing in a Downturn...Sorta

Like many other business managers, the current economic downturn has me wondering about how my strategy should change to meet new market realities. Because of this I have been reviewing different business periodicals and articles looking for advice. One of the best sources of managerial advice out there is The McKinsey Quarterly. For those who have not heard of McKinsey and co., Wikipedia describes them as  “…widely recognized as a leader and one of the most prestigious firms in the management consulting industry. …”. The goal of their Quarterly is stated as “…to help business people run their organizations more productively, more competitively, and more creatively.”


The people at McKinsey have published a lot of great advice over the years, and understand that many managers are currently looking for reading material about best practices and use of technology during the downturn. They have created a section in their Quarterly titled “Managing in a Downturn” where their most recent article is a great piece that promotes the intelligent use of existing IT assets to create new revenue.

Is one of the most revered business consulting firms referring to the use of Mashups as a way for companies to get themselves in a better competitive position in this economic downturn?

The team who wrote the article mention that an easy to-do is to use and combine existing data assets to gain new insight and business opportunities:

Few companies have successfully capitalized on the explosion of data in recent years. Often this information, residing in separate IT systems or spread across different business units, have never been mined for insights that could add value. Small teams of business and IT staffers can find opportunities by combining a detailed understanding of business processes with straightforward analyses of consolidated data sets……”

Achieving what McKinsey proposes can be a very long and arduous process using old-style integration technologies or for those companies interested in getting results quickly, Mashups are the perfect solution to easily and quickly combine all sorts of data.

The article goes on to mention an example of how a Telecommunications company improved revenue by

“…building high-value but inexpensive links between multiple silos of information. Contracts DB, sales funnels, compensations systems, CRM data warehouses, and other siloed systems… it facilitated analyses that uncovered opportunities to improve revenues…”

Wow! We are also seeing this type of use-case but not only in Telcos. Healthcare and Government arenas are having great results in providing better data by cross-analyzing many distinct data sources.

I know some of you must be thinking “he sees Mashups everywhere” (I do after all work for the leading Enterprise Mashup vendor) but you may only be partially correct in that statement. McKinsey may not be using the term but they are certainly talking about the value proposition of enterprise mashups.

Read More...

Tuesday, October 7, 2008

Mashups for the People. You Betcha!

I laughed when I heard Sarah Palin say in last week's debate: “...and I may not answer the questions that either the moderator or you want to hear, but I'm going to talk straight to the American people and let them know my track record also” (this is straight from the CNN transcript). I laughed because it’s such overt “spin” to say you’re not going to answer what the moderator wants to hear. And, incidentally, it's exactly what the moderator wants to hear.

But that’s beside the point. The point is that new technology companies are often put in a similar position of defending their new technology as a challenger to existing, established technology. This is certainly true in the enterprise mashup space. Since mashup adopters have started to graduate from “what-is-it-for” to “ahhh, here-is-how-I-can-use-it", we regularly have to compare and contrast mashups against existing technologies.

I think the defining "AHA!" moment is when people realize that mashups aren’t meant to integrate systems together like EAI/ESB software systems do. But rather that mashups are meant to integrate people to the data in their systems. And as an added benefit mashups are designed for collaboration and sharing among people.

So, now when we hear; “Oh, so mashups aren’t like my ESB or EAI systems that integrate systems; mashups get data from these systems to my people”, we give silent thanks to Sarah Palin, smile, wink, and simply respond with “You Betcha!”.

Read More...

Friday, September 26, 2008

Drowning in a sea of data or thriving as a Numerati?

I overheard two engineers joking the other day. One says to the other “There are 10 types of people in the world: those who understand binary, and those who don't”.

A couple days later I decided to catch-up on some reading and took up a dated edition of Newsweek in which I read a short excerpt from Stephen Baker’s great new book called 'Numerati'.  Baker posts a blurb in his website that describes the book as:

“A captivating look at how a global math elite is predicting and altering our behavior -- at work, at the mall, and in bed. Every day we produce loads of data about ourselves simply by living in the modern world: we click web pages, flip channels, drive through automatic toll booths, shop with credit cards, and make cell phone calls. Now, in one of the greatest undertakings of the twenty-first century, a savvy group of mathematicians and computer scientists is beginning to sift through this data to dissect us and map out our next steps. Their goal? To manipulate our behavior -- what we buy, how we vote -- without our even realizing it.”

I may be myopic but I think Mr. Baker is talking about enterprise mashups.

Reading the magazine article and excerpts, I started to think that it was odd that the ability to bring together and analyze data is perceived like a superpower. I can't say I agree that this is a skill possessed by a small elite or that the privileged few who have this skill who will dominate the ultra competitive and Über-data-centric (I like it when I can make up words) world we live in.

Certainly the ability to analyze reams of data is a task that requires special skills and dedication. However, JackBe's work and the experiences of the last few years with Enterprise Mashups has proven that the ability to gather data and to make sense of it consists more of a mind-set to which any intelligent professional can adhere to by implementing technology (such as Presto, our Enterprise Mashup offering).

We are seeing many use-cases (some of which we've been lucky enough to blog out) in which data from different applications and sources is being combined and filtered in innovative ways to find patterns that would not be easy to recognize otherwise. Some of these enterprise mashup implementations combine information from many internal systems to figure out who are the best people to work on a specific project. Others involve tracking numerous projects to ensure that everyone is aware of how their performance tracks to general company performance. We are seeing mashups solve issues in areas such as manufacturing, healthcare, pharmaceuticals and lots of others industries.

I now realize I extremely am fortunate to be involved in this industry and to be able to make an impact in the appearance of many Numerati and Numerati-savvy companies.

For those interested in learning about Stephen Baker’s book, Numerati, here is a link to a great slide show.

Read More...

Wednesday, September 17, 2008

What Google Chrome Can Teach Us About Enterprise Mashups

A few weeks ago Google announced Chrome, a next-generation virtual machine posing as a browser. While it looks and feels like a very minimalistic browser, the innovation isn’t the look and feel but rather it’s underlying architecture. In layman’s terms, each tab is its own mini browser running in its own environment. So, if one tab hangs or crashes, it doesn’t bring down your whole browser. The other architectural innovation is a JavaScript engine that significantly outperforms it’s peers. If you’re an Ajax developer, you’ve been waiting for this for a long time.

Equally interesting, Google added a nice marketing twist by introducing the world to Chrome through a cartoon. It turns out to be a great non-technical way to educate people as to what we’re missing by using IE/Safari/Firefox and why they created Chrome. I like this approach and it made me think about my own little techie world of enterprise mashups. How I could use this approach with my customers and prospects? Simple. I created my own comic strip with ‘Enterprise Mashup Dude’ in the starring role.

Enterprise mashups is a new, emerging category. Enterprise Mashup Dude’s first task is to help organizations understand exactly where mashups fits in their architecture. We’ve found that it’s quite common for IT folk to try to contrast and compare new technologies like enterprise mashup with existing technologies. This is both good and bad. It’s good because it’s IT’s job to identify new technology that can augment their existing technology. It’s bad when IT is threatened by such new technologies (they may view it as a disruptor to their incumbent technologies).

We also frequently encounter IT folks who understandably try to address enterprise mashup capabilities through their existing technology. In the case of enterprise mashups, the common comparison points include such as Data Warehouses, Business Intelligence (BI), Enterprise Service Buses (ESBs), and SaaS platforms like Salesforce.com. But there are many others as well and it would be an endless conversation if we had to compare and contrast to all existing enterprise technologies. So we came up with a clear and succinct phrase to cover 80% of the comparisons. The phrase is: “mashups don’t move data from system to system, they ‘mash’ data from systems to the user”.

But we can do better. We can illustrate this with a few “Chrome-toons” conversations between Enterprise Mashup Dude and a couple of friends:

(click to see the life-size Enterprise Mashup Dude)

I hope the point is obvious: mashups are different from ESBs, BI tools, data warehouses and even SaaS solution like Salesforce.com. They don’t integrate by moving data from one system to another. They mash data from multiple systems in real-time. It’s so simple a cartoon can explain it.

Read More...