An alternative to quarkus-jdbc-postgres that rather than instantiating a pgsql server, uses zonky embedded library, reducing memory footprint. It is mainly oriented for single pod k8s deployments or integration testing.
Include this dependency in your pom
<dependency>
<groupId>io.quarkiverse.embedded.postgresql</groupId>
<artifactId>quarkus-embedded-postgresql</artifactId>
</dependency>
You can now inject in your code a DataSource object (if you are JDBC friend) or a PgPool reference (if you prefer reactive) without adding any further property.
| property | description |
|---|---|
quarkus.embedded.postgresql.data.dir |
You can optionally persist information into file system by setting the desired path as value of property |
quarkus.embedded.postgresql.port |
You can optinally configure the postgresql server port by using this property. If no value is confirured a random available port will be selected. |
quarkus.embedded.postgresql.listen-address |
You can optionally configure the host(s) (listen_addresses) for the PostgreSQL server; if not set, localhost is used. Valid values include localhost, 0.0.0.0, ::, *, a specific hostname or IP (e.g. db.mycompany.local, 192.168.1.100), or multiple comma-separated addresses. |
This extension supports the usage of multiple datasources when the application has more than datasource which are defined by a specific name for each one of them, see the datasources guide for more details.
The extension uses the configuration of each named datasource matching the db-kind property to automatically create the databases on the embedded PostgreSQL for
each defined datasource and inject the proper configuration intro the application, such as the URL for the datasource.
Thanks goes to these wonderful people (emoji key):
 Francisco Javier Tirado Sarti 💻 🚧 |
 Ricardo Zanini 💻 🚧 |
This project follows the all-contributors specification. Contributions of any kind welcome!