Skip to main content
Prompts Java Data Access Best Practices Checklist

developer coding developer risk: low

Java Data Access Best Practices Checklist

Provides recommendations for Redis clients, JDBC connection pools, and ORM/persistence libraries, marking outdated or problematic options with ❌ and preferred modern alternatives w…

PROMPT 

🔴 1. Data Access & Connection Management
These are critical because they affect performance, scalability, and outages.

🔹 Redis
❌ Jedis (older pattern, topology issues)

✅ Lettuce (reactive, auto-reconnect)

✅ Valkey Glide (AWS recommended)

🔹 JDBC Connection Pool
❌ Apache DBCP

❌ C3P0

✅ HikariCP (default in Spring Boot, fastest, stable)



🔹 ORM / Persistence
❌ Old Hibernate 4.x

❌ MyBatis legacy configs

✅ Hibernate 6+

✅ Spring Data JPA latest

EXPECTED OUTPUT

Format
markdown

CAVEATS

Missing context
  • Detailed reasons or benchmarks for each recommendation.
  • Target environments (e.g., Spring Boot version, cloud providers).
  • Code examples or configuration snippets.
  • Success criteria for 'fastest, stable' claims.
Ambiguities
  • 'Valkey Glide' is mentioned without explanation or context.
  • 'topology issues' for Jedis not defined.
  • No specific versions beyond 'latest' or '6+'.

QUALITY

OVERALL
0.65
CLARITY
0.90
SPECIFICITY
0.75
REUSABILITY
0.25
COMPLETENESS
0.55

IMPROVEMENT SUGGESTIONS

  • Add specific version numbers (e.g., 'HikariCP 5.1.x').
  • Include brief pros/cons explanations with links to docs.
  • Convert to a table format for comparisons.
  • Expand with integration code snippets for Spring Boot.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR DEVELOPER