Do you execute ops in bulks or one by one?

Last bunch of the entries have been all about the code. Today let's try something different. Partly because at the time of writing I'm just 34 thousand feet above Atlantic and really don't feel like coding anything, but partly also because i have been thinking about the problem I'm going to describe for while already. I'm sure most of you have seen similar issue in the past as well or are fighting one such right now. So please don't be put out by the fact I describe it using Magnolia as an example because it exists in multiple other apps too. What I want to talk about is activation and scalability. Activation in Magnolia is an heterogeneous process that involves extracting the content from the author instance and transferring it over to one or more public instances where it needs to be re-imported and re-ordered to match the order in author instance exactly. And yes, you can already see the problem. Process of activation contains multiple steps that depend on each other and is easily serializable for a single piece of content. Which is exactly what have been done in the early activation code. First, content is extracted along with the ordering information, In the next step it is zipped and sent over http to all subscriber public instances where the ReceiveFilter picks up the incoming data, unzips it, locate the content that is being activated and replaces it with the incoming data. This is roughly what...

Date: March, 20 2010
Url: http://www.java.net/blog/rah003/archive/2010/03/20/do-you-execute-ops-bulks-or-one-one

Others News