Any JDBC driver provides abstraction for query/update result, so that driver can be changed at runtime without having to alter code accessing data through JDBC. Consequently, your JDBC code will behave in the same way whatever is underlying persistence: RDBMS or Acolyte.
Thanks to that, Acolyte can be used to test persistence code is doing what's expected when it's provided expected result by JDBC connection.
With advantages over using a test database, Acolyte approach can be performed going through following steps.
Once done, connection can be passed/referenced anywhere JDBC one is used.