monolith webapp, microservices, REST API, rich clients, etc.)Īll of these are interesting use-cases for jOOQ and trust us, jOOQ works everywhere. Your favourite architecture style (e.g.

Spring Boot, Quarkus, Micronaut, Dropwizard, etc.) Your favourite application framework (e.g.You might want to see an example of using in action, including Higher confidence when upgrading your production database, as that has already been tested (ideally, again, with testcontainers).A more streamlined jOOQ code generation process (always 1.Proper database change management is important, and jOOQ urges you to do it right up front in every new project. stored procedures, which are a great thing!) You can use all vendor specific features (e.g.Your quality will increase (despite using jOOQ, which can abstract over a lot, you will have production like behaviour in your tests as well, avoiding all sorts of edge cases that even jOOQ cannot handle).Instead, test your code against your production database product. The old days where you run MySQL, Oracle, PostgreSQL, SQL Server in production but test things on something like H2, HSQLDB, etc. Testcontainers is a wonderful utility that makes running non-trivial integration tests very easy, on docker. Currently:įor more details, see #1 Why testcontainers? RDBMS support for any RDBMS currently supported in the Sakila database.of the jOOQ Open Source Edition (in jOOQ-demo-oss).

of the jOOQ Professional and Enterprise Editions (in jOOQ-demo-pro).

It includes a variety of feature combinations including: A branch is available that works with a SNAPSHOT build of the dev version, which is available from: It depends on the latest released version of jOOQ. A jOOQ demo working with the Sakila database running in a testcontainers database instance (in docker).

Sakila demo database