Want Great Technology? Buy TIBCO (TIBX)

January 18, 2008

We all know that Oracle just bought BEA.

Personally, I would have recommended Oracle to buy TIBCO instead of BEA. TIBCO has great technology and their software stack is richer and more diverse that BEA’s. TIBCO spends a lot of  development resources on their graphical user interfaces and design-time and modelling environment to make business integration very easy.  TIBCO’s stockholders, like most great companies with a long history of the same executive management and management style, would greatly benefit from the acquisition.

Citigroup’s John Reilly Walsh upgraded TIBCO (TIBX) shares to Buy from Hold based on Oracle’s purchase of BEA. John thinks TIBCO, the last real middleplayer on the block, will also be purchased, and names IBM as the most likely candidate, “but adds that SAP, Hewlett-Packard (HPQ), Oracle (ORCL), Sun Microsystems (JAVA), EMC and Cisco (CSCO) all could potentially be interested.”

If Oracle bought TIBCO, a very interesting idea, that would leave Oracle the King of Integration (KOI). I don’t think HP, EMC or Cisco would want to purchase a company that is so fundamentally different than their core business.

This begs the question, should Sun buy TIBCO and challenge Oracle, now that Sun has purchased MySQL?

So the three most likely scenarios are:

  • IBM buys TIBCO
  • Sun buys TIBCO
  • Oracle buys TIBCO

In my opinion, the most interesting scenario would be Sun following their purchase of MySQL with a purchase of TIBCO. This could create a strong competitor to Oracle.

On the other hand, Oracle would benefit from the purchase, if only a defensive mechanism against a Sun/MySQL/TIBCO triple-threat, and they would get great technology at the same time.

I would be surprised if IBM buys TIBCO, but if they do, this would also keep things interesting!

From a cultural perspective, the TIBCO culture and the Sun culture are the best match.   I don’t think that the SAP or  IBM cultures are very suitable for TIBCO employess.  So, if you toss in the cultural perspective, Sun, cash rich and in acquisition mode, seems the most likely candidate to buy TIBCO.

The ART of Event Processing: Agility, Reuse, Transparency

January 18, 2008

The other day I discussed CEP in Layman’s Terms: Reuse and Agility. Today, our topic is CEP and transparency. One of the major benefits of “white box” event processing solutions is transparency, something not readily available or obvious in black-box solutions.

Friend and colleague John Bates, Progress Apama, often discusses the benefits of white-box algorithmic trading platforms in terms of increased time-to-market and other competitive advantages. I agree with John and would like to point out that there is another key benefit, in simple layman’s terms, transparency.

For example, let’s say you have designed an event processing solution for operational risk management (ORM). It is time for your favorite auditors to come by and they wish to take a look at what is going on with that proprietary black-box ORM application running quietly in the server room.

The nice auditors ask you, “What does that application do?” and you reply “Well, it looks for evidence of insider trading,” and they ask “Do you mind if we ask how?” and you respond “Good question, do you mind to wait a moment while I get you the contact info for the vendor because we don’t have access to the source code or the actual key indicators (KIs)?”

Now, let’s look at the white-box scenario:

Again, the nice auditors ask you, “What does that application do?” and you reply “Well, it looks for evidence of insider trading,” and they ask “Do you mind if we ask how?” and you respond “Yes, sit down and we will pull up our insider trading key indicator models. These models are stored in XML format and viewable in our graphical KI design studio. We can print out the KI models for insider trading if you like!” and the smiling auditor says “Thank you, your system is much more transparent than the last place we visited!”

This scenario also applies in looking for why certain KIs were not detected that should have been; or when performing a root cause analysis to see why the KI you used in your wrong business decision was inaccurate.

So, CEP in layman’s terms is what we might refer to as the ART of event processing:

  • Agility
  • Reuse
  • Transparency

Please feel free to reuse these idea, but please don’t forget to reference the author and this blog 🙂

Kindly share and reuse by reference, because all content in The CEP Blog is ©2007-2008 Tim Bass – All Rights Reserved. Thank you!

CEP in Layman’s Terms: Reuse and Agility

January 18, 2008

We often hear a lot about the core benefits of SOA, which include reuse and agility.

This week, I was in a meeting with Manoo Ordeedolchest, Board Member of Software Park, Thailand, Former President of the Software Industry Promotion Agency (SIPA), Former Dean, The School of Technology, Shinawatra University and a Lecturer at Chulalongkorn University, National Institute of Development Administration (NIDA), as well as other universities. 

We were discussing CEP and our proposed CEP Center of Excellence concept for Software Park.  One of the topics we touched upon today was CEP “in layman’s terms.”    After some brainstorming about CEP, it we were moved to draw a parallel between the SOA and CEP concepts of IT agility and reuse.

Just as SOA is centered around service component reuse and the agility to create new applications from service components quickly and economically; CEP can be considered to be centered around the reuse and sharing of domain knowledge, key indicators (KIs) and other intellectual property (like analytics) when processing events.

In an SOA, we modularize services and a service-component architecture in order to share services and build new applications from these service components.

One of the business goals of CEP is to modularize and standardize declarative programming logic and reuse this logic with event processing platforms from a variety of vendors.    This permits both reuse and agility when building event processing applications, at the application logic level versus the SOA service component level.

So, in laymen’s terms CEP can be discussed using the same SOA concepts of reuse and agility, applied to event processing application logic and KIs.

In a future post, I will talk about about CEP and transparency in layman’s terms.