anybody using JDBI or HikariCP?

# server

[asad.awadia]

anybody using JDBI or HikariCP?

[Attila Domokos]

We evaluated Exposed and JDBI and went with JDBI.

[asad.awadia]

what DB? postgres?

[Attila Domokos]

yep

[asad.awadia]

How are you doing connection pooling? Does JDBI only make one connection?

[Attila Domokos]

We are at the very beginning of the project and we have not set up connection pooling. We will though.

[Joe]

we use hikari w/ jooq: https://github.com/trib3/leakycauldron/tree/master/db

[Joris PZ]

We use HikariCP all the time, very good and stable pool implementation

[Anders Sveen]

Been using JDBI+Hikari in production for a while. No issues at all, if that's what you're worried about. 🙂

[tipsy]

also using jdbi+hikari

[asad.awadia]

How do you model your DAOs when joins are involved?
eg if I have a customer that can have many orders - and I have a customer dao and an order dao — how do I get the Joined relation?

[Anders Sveen]

I tend to just use IDs between two separate aggregate roots. So no real navigation within the domain. If you have like an order with an address I do all of that in the order dao.

[asad.awadia]

@Anders Sveen so the order dao will query the address table?

[Anders Sveen]

Yeah. Or depending on the structure, just a join so we get a single query. If I have to make decisions based on two aggregate roots I put that in a service, or better yet I do order.smoethingMethod(customer) .