This blog entry describes how WebSphere eXtreme Scale uses memory. This allows customers to better size how much memory they need when storing a large number of key value pairs in a grid.
The text is in my personal blog at this link.
on Oct 28, 2009
Yesterday, I said the most important aspect of an XTP platform is the management. Automatic placing of data on a grid of computers, automatic scale out as new boxes are added and automatic replica count maintenance as boxes fail or are taken out of the grid. It's this aspect which makes extreme possible as it makes writing applications very easy as all the management is taken care of.
on Feb 22, 2008
I was explaining XTP in a meeting this morning and covered the usual aspects. It (in the form employed by ObjectGrid and its gigoherence competitors) uses replicated memory based storage for persistent state AND it uses a self healing/scaling grid to deploy that storage fabric on.
Someone asked if XTP is just about memory based replication then? I said no. If it was just about memory based...
on Feb 21, 2008
This is a great question. Depending on who you ask, you get a different answer. Vendors will pitch what they think and why competitors are wrong. I guess I just want to put out what I think it is so here goes.
Topology wise, there are three styles. The fixed number of partitions where records hash to one partition is the first. This is typical of the default mode of ObjectGrid and...
on Feb 5, 2008