Chapter 13. Taming wild EJBs: performance and scalability
This chapter covers
- Entity locking
- Performance improvement of JPA entities
- Tuning of session beans and MDB performance
- EJB clustering
When it comes to building software systems, it’s the end that matters—not the means. Working, reliable software that is usable is what it all boils down to. In the end, what customers care about is that your product produces consistent results, performs well, and meets scalability and availability requirements. Most developers and users can agree on that. But then there’s the part they can’t always agree on—the part that’s implied and expected by the users, but not always understood by the developers. Surely you’ve seen it before. You just finish plopping your latest new-fangled application into production and the e-mails start flying and the calls come rolling in. It turns out that the users had some other expectations as well. Something about how they expected the program to perform. Sure, the application has the features they asked for, and everything appeared to work during user acceptance testing (UAT), but now that it’s in production everything’s so slow. Can anything be done?