Friday, December 9, 2011

WXS competes with Oracle Coherence

The purpose of this discussion is to compare the IBM WebSphere eXtreme Scale (WXS) product with Oracle Coherence, specifically their architectural differences. While on the surface they may seem interchangeable, digging beneath to understand the fundamental architecture is required to make a better choice and decision

Basically:

I do not focus on feature gap, sooner on later we catch up and one up each other.

I focus on core architecture differences such as

a. Server to Server Communication - WKA - Well Know Address/design based on multicast which is more of an after thought. WKA disables multicast which limits scalability in Coherence architecture.

so while performance should be comparable we all access data from memory, but where we should differ due to architecture is scalability, we should scale easier and painlessly than oracle coherence... which is an important yet subtle distinction.

b. Client to Server Communication : Oracle Coherence requires gateway processes for TCP Extend to work that incurs significant CPU and network latency hops. Also this is more of an after thought.

c. I would ignore any performance claims, because at the end of the day we all access data from memory, --- If someone presents this to me, I would want details and would want to know why? What is so special that gives anyone the X perf advantage?

Coherence one up WXS with C++ integration– which WXS will soon address, however I still think that a common grid between Java/.Net and C/C++ application is utopian, and not practical.

Net-Net : WXS competes on Scalability claims and NOT Performance, Superior Architecture and feature comparison, and Thought leadership and not historical presence.

Thoughts?
:)
Nitin

No comments:

Post a Comment