Document prepared-statement affinity semantics and performance tradeoffs in multinode OJP

[Copilot]

This addresses the open question on whether prepared statements are effectively sticky in multinode OJP and what that means for performance. The new analysis clarifies that prepared-statement reuse is session/connection-scoped, so realized gains depend on maintaining session affinity.

• Findings document

  • Added documents/analysis/PREPARED_STATEMENT_AFFINITY_ANALYSIS.md.
  • Captures the behavior contract:
    • server-side prepared statements are session-bound
    • driver routing is session-to-server sticky
    • statement UUID reuse assumes session continuity
  • Summarizes performance outcomes by traffic pattern (high affinity vs low affinity).

• Analysis index update

  • Added the new document to documents/analysis/README.md under latest analysis.
  • Updated the index timestamp.

// Effective reuse boundary in OJP multinode mode
PreparedStatement ps = conn.prepareStatement("SELECT ... WHERE id = ?");
ps.setInt(1, id);
ps.executeQuery(); // reuse benefits depend on the same session/server affinity

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud