There are technically two questions here, but they are closely related :)
I am using Hibernate in a new project. This is a POS project . It uses an Oracle database.
We decided to use Hibernate because the project is large, and because it provides the (most popular) ORM features.
Spring at the moment is out of the question: the reason is that the project is a Swing client server application, and it adds unnecessary complexity. And besides, Spring has to be very hungry on hardware resources.
It is possible to throw away Hibernate and use JDBC. What for? Requirement for the project precise interaction with the database . It’s clear that we must have full control over connections, sessions and transactions (and, yes, as low as unoptimized requests).
First question: what is your opinion on the use of this application?
The second question revolves around Hibernate.
We developed a simple Hibernate pilot project. Another project requirement is one database user / one connection per user / one session per user / transactions are flexible (we can end them as we want, as sessions) .
Multiple users can simultaneously register an application .
- . , .
, , , ( ), SessionFactory, ConnectionProvider . ?
, .
: , , Hibernate .
.