.

In this way, is hibernate worth it?

The straight forward answer is YES, every thing is worth to learn in spring MVC, orm hibernate as still in any company you work you will get a chance to modify or add new files, classes, mappings and without having the knowledge you may find it difficult to think where to start what to code, sometimes a small.

Secondly, is hibernate still used? But in my experience, JPA and Hibernate are still a good fit for most applications because they make it very easy to implement CRUD operations. The persistence tier of most applications is not that complex. It uses a relational database with a static domain model and requires a lot of CRUD operations.

Simply so, why Hibernate is better than JDBC?

Hibernate provides transparent persistence and developer does not need to write code explicitly to map database tables tuples to application objects during interaction with RDBMS. With JDBC this conversion is to be taken care of by the developer manually with lines of code. Hibernate provides this mapping itself.

Why JDBC is faster than Hibernate?

Performance: Native JDBC is faster than Hibernate because of the latter's need to generate queries on the fly. Server customisation, partitioning and so on can mitigate this though. Scalability: If an application is not likely to grow beyond a small number of database tables, then native JDBC should be adequate.