java-utils VS sqldb-logger

Lead Engineer at PAX Labs, we just open-sourced some Java utilities i wrote in the early days building service oriented architecture on dropwizard: https://github.com/PaxLabs/java-utils

A few things in there:

* `HibernateQuery` - wrapper around hibernate jpa implementation, because using the jpa criteria api is verbose as hell (seriously, even for java). Coming from having written Django, I wanted the ease of using Querysets in java

* Makemigrations - this seemed to be a missing hole in the java ecosystem. Our contractors were hand-writing sql migrations and using some framework that just ran them. Liquibase exists for managing migrations, hibernate can generate the schemas. This library is a dropwizard command to generate yml to migrate the old schema to the new one.

* generic pagination bundle

You can use this to get instant query logging for sql.DB. https://github.com/simukti/sqldb-logger

sqldb-logger: https://github.com/simukti/sqldb-logger

It's a thin layer that wrap Go (Golang) SQL database driver, it does not change sql.DB usage in any existing Go app.

It is because I prefer to use vanilla Go sql.DB in my web service and I could not find any SQL logger for Go SQL database standard library that can use structured JSON logging.