DB2 Java Performance Standalone Transactions Part 2

Another situation when a transaction runs into problems is when it must check something outside of the critical transaction path or its normal activity. For example, when a transaction uses seven different discrete web services to accomplish a complete transaction unit-of-work and after the third web service runs into a situation where something else needs . . . → Read More: DB2 Java Performance Standalone Transactions Part 2

DB2 Java Performance Standalone Transactions Part 1

In previous blog entries I have talked about transaction scope, how DB2 Java applications access the database too much and transaction units of work (UOWs) are not really analyzed properly.

Too often these days the design and development are done in an Agile or SCRUM type of project methodology where short concise project deliverables are . . . → Read More: DB2 Java Performance Standalone Transactions Part 1