JDBC implementation at persistent layer side in spring
posted 10 years ago
I would not base the decision on the number of users but in the complexity of the query you want to execute. In my experience, the convenience that Hibernate provides is usually worth any overhead when it comes to simpler queries. Once you start having more complicated queries involving multiple joins and/or more than two tables, then overhead becomes more of an issue. If you program to DAO interfaces, it is easy enough to switch from a Hibernate implementation to a JDBC implementation.