How scalable is Hibernate?The information on this page helps you when looking for Hibernate's deployment scenarios and give you some impression about the scalability of the framework. If you are interested in contributing your own project details to this page (anonymously), click Edit this page in the top right corner. Thanks!
Short project description (web-based, client/server, etc.): Use this as a template! Hardware (Servers, Loadbalancers, etc.): - Software (Operating System, JDK, App Server, etc.): - Database Details (Product, Version, Tables/Views): - Concurrent Users (read or write?): - Special Hibernate tricks (Cache, Long Session, etc.): -
Short project description (web-based, client/server, etc.): Web-based training application with seperate "faces" for back office administration, employee training, and public training (customer and partner). The data is actually stored as part of a much larger CRM database. Hibernate is used to map the portion of the schema used by the training application. Hardware (Servers, Loadbalancers, etc.): One app server running on a 4GHz / 4 Sparc Sun server; one DMZ webserver running on a 2GHz / Dual Sparc Sun server; database running on an HA AIX cluster. Software (Operating System, JDK, App Server, etc.): Bea WebLogic 6.1.5 running on Solaris7; Vignette Application Portal 4.5.1 hosted in the WebLogic instance; IPlanet Webserver running on Solaris7 Database Details (Product, Version, Tables/Views): Oracle 8.1.7.4 hosting the entire CRM database (the training app uses 93 of these tables) Concurrent Users (read or write?): Admin site (highly transactional): ~20 users; Employee site (mainly read/search, some writes): ~40 users; Public site (mainly read/search, some writes): ~70 users Special Hibernate tricks (Cache, Long Session, etc.): Extensive use of Interceptor for: 1) Audit data; 2) Change tracking; 3) Event propogation and MOM integration; 4) Cache invalidations; 5) Integration with custom validation framework
|