Is open source software a deli or a bee hive?
I really like using analogies and metaphors to explain things. I think good ones catch on quick and get carried further and further until they sound ridiculous - but that's when you know there was a grain of truth to them. Two that I've heard recently that really worked (or at least got used over and over again!) are open source software as honey and open source software as a deli.
Open source software model = Bee Hive
James Dixon originally wrote the bee and honey analogy in the The Bee Keeper. His analogy is:
- The open source community are bees,
- The open source software they produce is honey,
- Companies that foster or "own" open source software are beekeepers, they create an environment that fosters honey creation.
- Companies are processed honey eaters or "supported" software.
Matthew Aslett takes the idea even further. He applies it to companies that certify and support open source software, as well as those that have proprietary and open source software solutions and even pure open source software projects with no commercial company attached. He starts by pointing out that there are two types of honey: domestic honey (company owned projects) and wild honey (community only projects).
In his model, OpenLogic is a "honey collector":
There are some consumers (adopters) that might prefer the taste (and low cost) of wild honey and are happy to go to the effort of collecting it and processing it for themselves. However, if they do not want to take the time or the risk to do so instead they might pay a honey collector (support provider) to do the job for them.
While the honey collector does not have responsibility to look after the bees that a bee keeper has he will have to take care not to disrupt the nest and may well choose to make an effort to nurture the nest and encourage honey production. Of course, as these are wild bees there is also always a risk that the bees will leave the nest or production will dry up.
OpenLogic is also a "blender":
blenders (service/certification providers) that pick and choose honey from a variety of freely available bee nests and blend it together to produce a more palatable product.
And then there are "brewers", companies that create hybrid products of open source and proprietary software:
An example would be a brewer of mead. A brewer could of course choose to develop his own honey using man-made hives or acquire honey from a bee keeper, but by exploiting wild honey he lowers production costs and focuses on the additional value he brings to the production process.
Open source software = Deli
A couple of weeks ago I was at an HP event where r0ml gave a talk "The Software Deli". His analogy was that proprietary software is like automobile manufacturing and open source software is like sandwich manufacturing. You don't go into a deli and order the same sandwich as everyone else. You go into the deli and you pick and choose what kind of bread, what type of meat, type of cheese, … that picking and choosing and custom software is a lot like how companies use open source software. I knew it was a good analogy when ever speaker after him, and everyone that asked a question, tried to frame their thoughts in terms of sandwich making! The talk was recorded and should be on the web soon - I'll add a link when it is.
Got any more good open source software analogies?



The power of the “Software Deli” metaphor may be in its inapplicabilities: I really can’t recall ever visiting a deli and being told “you can’t have Swiss Cheese version 1.0.3 with your Rye Bread 2.7 unless you switch out your Virginia Ham 8.0 for a Processed Ham Loaf 37.3. But then you’ll need mustard 6.8 instead of 6.9, and that doesn’t go with dill pickle 4.0 … how about a nice bag of chips instead?”
But you *know* we dance that dance all the time, with software in general and particularly with open-source software.
Which is where, of course, the “collector” really earns her pay!
To me the software deli analogy seems to lack any notion of a community. It only describes two very different businesses.
Who or what is ‘the deli’ in this analogy? It cannot be a single open source project as each project typically only generates a single ‘ingredient’. Maybe you could consider Sourceforge to be the deli? This analogy does not go very deep.
James Dixon
[...] Theodor Ts’o opened a conversation about organic vs non organic open source development, following a Mozilla’s organic definition. Matthew Aslett later reopened the discussion further exploring the bee keeper analogy, getting some reactions from Stormy Peters and James Dixon (original author of the Bee Keeper model). [...]
I’m not sure if Blender is quite the right analogy for both service & certification providers - maybe only the former.
For instance, under the Java JCP, a JSR lead will provide & license a TCK, thus enabling certification. This is more like a trusted independent or government body stamping a jar of honey with the honey’s provenance - to ensure that it meets all food standards.
But maybe I’m just stretching the analogy too far…