datasource-proxy VS Hibernate

There is a cool library called datasource-proxy. It provides a convenient API to wrap javax.sql.DataSource interface with a proxy containing specific logic. For example, we can register callbacks invoked before and after query execution. What's interesting is that the library also contains out-of-the-box solution to count executed queries. We're going to alter it a bit to serve our needs.

In this option, we wrap our HikariCP instance in another object. The nice thing about this option is that it can be used with any connection pooling library (not just HikariCP); but, it does require that you add an additional dependency to your project: https://github.com/jdbc-observations/datasource-proxy

And Hibernate ORM is LGPL: see the license on their Github project.

13. Hibernate

Hibernate is the umbrella for a collection of libraries, most notably Hibernate ORM which provides Object/Relational Mapping for java domain objects. In addition to its own "native" API, Hibernate ORM is also an implementation of the Java Persistence API (jpa) specification.

I'm using Spring Data JPA as a persistence framework. Therefore, those classes are Hibernate entities.

I'm a top Hibernate contributor

Hibernate -- https://hibernate.org (huge learning curve)

This video is a crash course into the Hibernate & JPA universe.

To prevent SQL Injection attacks to sanitize input data. You can either validate every single input or validate using parameter binding. Parameter binding is mostly used by developers as it offers efficiency and security. If you are using a popular ORM such as sequelize, hibernate, etc then they already provide the functions to validate and sanitize your data. If you are using database modules other than ORM such as mysql for Node or Mongoose, you can use the escaping methods provided by the module. Let's learn by example. The codebase shown below is using mysql module for Node.