Also kind of a newbie question: When using next.jdbc , how does it handle asynchronicity? I see that a query will wait for the previous db query to return, which is useful if you have db queries that depend on previous query results, but should I use core.async for times when I need parallel queries or is there a better way?

@ovidiu.stoica1094 JDBC is inherently a synchronous API

so it doesn't handle asynchronicity at all - it just blocks

(sans some extensions for particular dbs)

> should I use `core.async` for times when I need parallel queries or is there a better way? Connection pooling - via HikariCP or C3P0 - should be your first step for when you have multiple threads that need to make queries