Add tests for Ktor using an async database layer #4247
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a couple additional tests with Ktor, but using non-blocking database clients. In theory this should reduce the overhead of using blocking JDBC calls with a work pool.
I actually went ahead and implemented two different clients since I'm curious how they perform. Jasync-sql is interesting in that it has Kotlin coroutines integration, which makes the code actually more natural than the JDBC based tests. Reactive-PG-Client seems more feature full, and is the same client used in the Vert.x tests.