Building an Ecosystem from mSA?

Recently BEA has been talking a lot about their new MicroServices Architecture. By leveraging OSGi they contend they will be able to more rapidly and effectively compose middleware environments. The way it is described though, it seems to me that the advantages are all internal. From the point of view of a customer, I think a valid question might be, “who cares?”

I think BEA could be leveraging this new MicroServices Architecture (mSA) much more effectively to build an eco-system of community in much the same way that Firefox has. By opening up the OSGi bundle-level api’s, or even better, the source itself, BEA could encourage the development of an entire ecosystem around their core middleware services.

Within the defense space I can think of a number of other companies that are embracing OSGi for the same fundamental reasons that BEA is touting; things like rapid composability of capabilities in the run-time. I believe those companies would leverage core BEA capabilities for networking, thread pooling, standards interoperability etc. if they could do it at the Chinese menu level.

Maybe BEA *is* thinking about it this way but their marketing to date doesn’t express it that way. It seems to talk more in terms of the internal benefits to BEA of mSA as a product strategy; much the way Ford might talk about their “world car” platform.

Comments

  1. Kit Plummer - August 28, 2007 @ 6:18 pm

    Sounds like ServiceMix 4.0 is what you are looking for.

    BTW, do you own a big wad of BEA stock?

  2. Jim S - August 28, 2007 @ 10:02 pm

    @Kit: I think a little bit lower level than servicemix, but i see your point.

    Nope, I would never own any technology stocks. 😉 But like I said in my last post, I was in a meeting with BEA this week and it got me thinking a bit about their traditional middleware software model in the face of an upward creeping OSS stack.

Leave a Reply

Your email address will not be published / Required fields are marked *