Don says that BEA's Deputy CTO has missed the cluetrain. I absolutely agree with Don's opinion on this article and what's even worse than the things said is what the article implies. If that is BEA's official position, this is nothing less than an outing that they are passengers in the backseat of a car that is driven by IBM and Microsoft (switching drivers every once in a while) and that they're neither behind the spirit of the whole undertaking nor do they fully understand the specifications they have put their names on. Integration or standardization on the API level has failed miserably in countless attempts and any middleware company (including BEA) that is out there to compete on features must go beyond the least common denominator approach to win over customers. Does BEA have Indigo envy?
You May Also Enjoy
A New Network - Rethinking Addressing and Routing.
24 minutes read
Considerations for introducing a logical addressing model for the AMQP Addressing specification that coexists and integrates with the common IP/DNS addressin...
AMQP. The Road Ahead.
11 minutes read
A summary of what’s next for the AMQP messaging standards suite and why digital messengers will want to come join the technical committee to help.