Open Source Unleashed

Open source, solutions and what it takes to pursue a middle ground

In my last post I attempted to overlap what it would take to establish a middle ground and the concept of open source driven solutions.  I'm not sure how well my point went across, but I am certain that the notion of a new wave of solution that not only includes, but is rooted in openness is one that's here to stay. With that in mind, I think it's relevant to look into what it will take to facilitate the shift towards flexible, truly open solutions. More than anything I think this entails a change in perception regarding what/how sizable a role open source will play in the mostly nebulous world of "solutioning." In effect, what needs to happen in order to kick-start the evolution of open solutions from embryonic towards maturity?

To those allergic to buzzwords, the term solution might incite a sneeze. However, upon further examination a great deal of technology is delivered as a solution, that is a bundled, ready-to-use component. The consumer technology market, by itself, is rife with examples (see: the iPod, most home PCs). And while the concept that consumers want to purchase products that fit a specific niche practically out-of-the-box, the notion that the same holds for large companies isn't as evident. To be fair, it's not possible to mass produce ready-made technology for organizations with narrowly defined business requirements and use-case scenarios. And in the case of open source, there are hardcore realities that stand in the way of it playing a larger role in driving greater time-to-value and cost efficiency:

• Integrated designs. One solution size does not fit all and the fit is typically determined by the industry in question. This implies a knowledge of specific segments drawn out in the form of industry solution maps.
• The importance of the sales cycle. Solutions are sold, first and foremost. Open source is still being stealthily transported into a great deal of enterprise environments with the sales process a shortened after thought. If the notion of open source solutions is to take hold, it must be sold and accepted wholeheartedly not smuggled in and permitted to stay afterwards.
• Overlap with industry proven models, best practices and methodologies is key. Acronyms like CBM, IFW and BPM might not be everyday terms but they are industry proven and widely accepted as the basis for solutioning.
• The criticality of a top-down approach that initially prizes business value over technology. I won't pose the bottom-up mentality that has buoyed the open source software movement for some time now, against the seemingly inherent top-down nature of most hierarchies. However, it pays to note that technology selection/procurement is at its core a business decision. And unlike individual products, integrated solutions speak more to the business side of things than anything else.

Finally, if open source solutions are to evolve they must rely on more than being cheaper. Especially since the marketplace tends to base its decision on more factors than just price alone. The market for solutions is driven by participants who exhibit demand for addressing their industry-specific performance drivers, are modular and customizable. Add to the fact that providers which can accelerate time to value, reduce risk and deliver integration are its leaders and it becomes evident that the road to broadly relevant open source solutions is a tough one, indeed.

Technorati Tags: solutions |  open source software

Pursuing a middle ground

Note: I'll start this blog post off with an acknowledgment to those who have posted comments on my main blog site (http://alexfletcher.typepad.com) for the past two-and-a-half months. I have been unable to view newly posted comments through my TypePad administration console since earlier this year. I was unaware of the fact until after a recent maintenance outage for TypePad I was able to see the deluge of comments that have been posted. I have yet to determine exactly why this was the case, but am looking into it.

On that note, Redmonk's own, Cote' left me a comment (on this post) two weeks or so that struck me as thought provoking.

"What would you add - if anything - about using organizations like the Eclipse Foundation, the ASF, or other standards/code bodies to have a sort of neutral-ground and/or organization "middleware" for all this?"

While the concept of middleware that sits between an increasing array of quality software, produced as output of the open source development model, sounds abstract the growth in demand for open source has created a void for just that. This middle ground is essentially a nether region between software vendors/system integrators and the businesses looking for last mile solutions. Typically, for the larger companies and organizations it's players like IBM GBS and Accenture Global Services that go that last mile to deliver the notion of an integrated solution (excuse my marketing-speak). However, this is done taking a proprietary approach (products, tools and processes). Which proves wildly profitable for both of the aforementioned companies, still what has yet to be seen is who will play the role of coagulating some of the disparate sources of open source, refining it and delivering as consumable pieces that meet a specific business need.

I'm a big proponent that software is bought for what it does instead of what it is. High-end ERP implementations don't ring up 7-8 figures on account of simply being an ERP rollout, rather it's the fact that these systems are often the lifeblood of modern business operations. And there's a growing role for open source within the context of ever narrowing market segments. The Eclipse Foundation has caught wind of this reality and begun to branch out in the direction of specialization. And they're not alone, the OSA has made headway towards giving life to the open solution. These efforts will be instrumental in making open source feasible for segments such as the SMBs, microverticals, service industry verticals and emerging economies.

This is precisely where the middleware analogy is applicable. In the case of organizations like Eclipse and the Apache Software Foundation they are the glue/packaging that enable that sits between the raw productive power of the open source software model and the industry-specific needs of its consumers. Strangely enough, the need for a middle ground goes almost entirely unmentioned. Yet in the absence of an established group of open source behemoths that influence macro-level trends increased prevalence of organizations that serve as a neutral buffer is a positive. Realistically, these organizations don't even have to resemble Eclipse or Apache. And I fully expect that more OSA-style groups will sprout, as profit-turning entities like SIs or vendors begin to realize that it works to their benefit to cooperate towards delivering a collectively neutral approach to "solutioning."

Whether this middleware is spurred by marketplace demand or the proactive foresight of players in industry has yet to be seen. Additionally, increased consolidation amongst open source participants might bring about de-facto platforms fit with ready-made ecosystems that can standalone from one given end to another. However, to wait for impending consolidation is reactionary and strategically sloppy, at best. Especially since in the light of every acquisition (large and small) there is considerable room to pursue the middle ground.

Technorati Tags: solutions | open source software

Towards more progressive open source

I found Oracle's statements on open source, tendered at the Linux/Open Source on Wall Street conference, intriguing to say the least. I'll begin by making it clear that I don't doubt the veracity of the database giant's experience with its customer base. In fact, I take Monica Kumar's word when she says "We haven't seen our customers asking for open source databases...Not many customers are interested in looking into the code and mucking around with it, and making changes to it." Honestly, the latter half is almost taken as established fact, especially as it relates to infrastructure software like databases, middleware, etc. Unfortunately, pointing this out does more to pawn off the entire open source value proposition solely as visibility into source code.

Strangely enough, I don't actually expect Oracle to recognize the varied dimensions of open source on account of having too much vested in the proprietary model, industry leaders can be funny that way. As Matthew Aslett over at the 451 Group points out, "It is no wonder Oracle hasn’t seen customers asking for open source databases - it has been busy looking the other way." On the other hand, I'm sure the folks at Sun might disagree with the contention that there isn't a notable demand for open source databases.

Still, you would think that in an age marked by global conglomerates, rapid consolidation and break-neck competition, there is sufficient motivation to recognize how to fully leverage open source. And just as much room to express how to do just that. However, stock barrel line on open source remains, more or less,

1. Cheaper
2. No vendor lock-in
3. Better???

The first of which is being diluted by the dynamics native to any marketplace, see: the availability of products like Oracle Express. Number two still holds true, although to those already chained to a proprietary vendor/platform the talk of freedom of choice mostly comes across as just that, talk. Which is precisely why I'm of the perspective that there's room for what might be termed as progressive open source. Yes, this terminology drips with political overtones, but pragmatically I think open source success, over the long haul, will be achieved by tending towards more progressive characteristics.

Thus far it has been well-established that open source is indeed different. What's needed now is to demonstrate how these multiple degrees of difference can help meet customer needs, solve complex business problems and power innovation. Up to this point, this brand of understanding has resembled esoteric knowledge more than it has mainstream thought. And that's exactly what needs to change. More need to be informed what is to be gained from open source and why it matters to them. Instead of open source = cheaper and more open, it should be: Yes you will save money, yes you won't be locked in, but here's how involvement with an open community is profitable as well.

The root of progressive is progress, which can't be achieved without a break from the stat quo. However, to overcome the inertia that can stifle progress an alternative mode must become real. Its benefits can't be vague and hazy. The reasons to embrace a shift from established avenues can't be known only to an inner circle of the "enlightened" but should be expressed to the collective whole. This takes time, but the passing of time itself shouldn't be mistaken for gaining ground...its progressive action  applied over time time that breeds a desirable end result.

Technorati Tags: Oracle |  open source software | openness   

Towards more progressive open source

I found Oracle's statements on open source, tendered at the Linux/Open Source on Wall Street conference, intriguing to say the least. I'll begin by making it clear that I don't doubt the veracity of the database giant's experience with its customer base. In fact, I take Monica Kumar's word when she says "We haven't seen our customers asking for open source databases...Not many customers are interested in looking into the code and mucking around with it, and making changes to it." Honestly, the latter half is almost taken as established fact, especially as it relates to infrastructure software like databases, middleware, etc. Unfortunately, pointing this out does more to pawn off the entire open source value proposition solely as visibility into source code.

Strangely enough, I don't actually expect Oracle to recognize the varied dimensions of open source on account of having too much vested in the proprietary model, industry leaders can be funny that way. As Matthew Aslett over at the 451 Group points out, "It is no wonder Oracle hasn’t seen customers asking for open source databases - it has been busy looking the other way." On the other hand, I'm sure the folks at Sun might disagree with the contention that there isn't a notable demand for open source databases.

Still, you would think that in an age marked by global conglomerates, rapid consolidation and break-neck competition, there is sufficient motivation to recognize how to fully leverage open source. And just as much room to express how to do just that. However, stock barrel line on open source remains, more or less,

1. Cheaper
2. No vendor lock-in
3. Better???

The first of which is being diluted by the dynamics native to any marketplace, see: the availability of products like Oracle Express. Number two still holds true, although to those already chained to a proprietary vendor/platform the talk of freedom of choice mostly comes across as just that, talk. Which is precisely why I'm of the perspective that there's room for what might be termed as progressive open source. Yes, this terminology drips with political overtones, but pragmatically I think open source success, over the long haul, will be achieved by tending towards more progressive characteristics.

Thus far it has been well-established that open source is indeed different. What's needed now is to demonstrate how these multiple degrees of difference can help meet customer needs, solve complex business problems and power innovation. Up to this point, this brand of understanding has resembled esoteric knowledge more than it has mainstream thought. And that's exactly what needs to change. More need to be informed what is to be gained from open source and why it matters to them. Instead of open source = cheaper and more open, it should be: Yes you will save money, yes you won't be locked in, but here's how involvement with an open community is profitable as well.

The root of progressive is progress, which can't be achieved without a break from the stat quo. However, to overcome the inertia that can stifle progress an alternative mode must become real. Its benefits can't be vague and hazy. The reasons to embrace a shift from established avenues can't be known only to an inner circle of the "enlightened" but should be expressed to the collective whole. This takes time, but the passing of time itself shouldn't be mistaken for gaining ground...its progressive action  applied over time time that breeds a desirable end result.

Technorati Tags: Oracle |  open source software | openness