You know how when you say a word too many times, it loses its meaning?
Performance. Performance. Perfromance. Perfroamnce. Prefroanmce. Prefornacme. Hold the door!
Sometimes that happens with “performance,” especially when there are so many points of failure which are out of your control. But one thing you can control as a developer, is how your code uses the database.
Check out this slideshare that presents 4 JPA best practices for better application performance. And don’t forget that only you can prevent
forest production fires. (Smokey the Bear, anyone?)