HikariCP
Kotest
HikariCP | Kotest | |
---|---|---|
33 | 17 | |
19,424 | 4,289 | |
- | 0.7% | |
6.2 | 9.4 | |
about 1 month ago | 4 days ago | |
Java | Kotlin | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
HikariCP
-
Java virtual threads caused a deadlock in TPC-C for PostgreSQL
Looks like HikariCP is also awaiting fixes for this https://github.com/brettwooldridge/HikariCP/pull/2055
- About Pool Sizing
- HikariCP maximumPoolSize based on AWS ECS number of tasks
-
Writing to db
I have used hikari and exposed to do this in the past with postgres, although other dialects are supported.
-
A Tale of Two Connection Pools
I found one suggestion from the author of HikariCP on how to address this, which I implemented and it worked. However, there are additional classes involved, and it feels a little clunky and hard to follow.
-
Spring boot change password runtime
Not really, you can change some things in spring boot but doing so will typically trigger a refresh which is less reliable than restarting but still causes a large performance hit. You could probably do it with hikari if you really needed to but it's inadvisable to build your application around this mechanic.
-
Help with bungeecord server
# https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing
-
Currently load testing a Django API I don’t get good results, Help me brainstorm this
Not familiar with Python but this thread about a Java connection pool might be interesting: https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing
-
Should I use diesel ORM if performance is the most important thing?
Whatever you choose, presuming your app is database heavy, I highly recommend spending time on DB schema design to make all queries as short as possible, avoid relying on transactions, and keep your connection pool tiny. For reference: https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing
-
Art of README
You reminded me of the HikariCP library and it’s documentation: Clear and simple with references to other libraries trying to accomplish the same thing. It is not in the closure space though.
https://github.com/brettwooldridge/HikariCP
Kotest
-
AocKt: Test-driven Advent of Code in Kotlin
As you might know, Advent of Code will begin this Friday! If, like me, you want to have a go at solving the puzzles in Kotlin, I would like to share with you a little library I've developed to reduce boilerplate and solve the puzzles in a test-driven approach. It is based on Kotest, a modern and Kotlin-first test framework.
-
Tests Everywhere - Kotlin
Kotlin testing with Kotest and MockK
-
Best practices for Unit Testing Android Apps with Mockk, Kotest and others
As a matter of fact, in the previous examples, we have shifted a bit away from the TDD standards in the meaning that we test not only the operability of our code, but rather check if the code runs according to certain specifications (Given/When/Then). These specifications are our tests, and the syntactic sugar in the form of the possibility to give clear names to the tests using DisplayName and the grouping of the tests by a set of similar attributes helps us clearly formulate these specifications. There is an entire family of frameworks in different languages that allow us to create such specifications: for Java it is Spock, for Ruby—RSpec, and for Kotlin—Spek and Kotest frameworks. Below, I will go into more detail about them.
- Why do Kotlin tests (for Gradle projects) have to be inside classes?
-
Kotlin Mutation Tests
I've tried so many times. SO MANY. I love the idea of mutation testing. Even chatGPT couldn't help me. It just made up fake mutation testing frameworks to try. To me, pitest is dead. kotest is not mutation testing, but it's property testing is the next best thing I have found to revolutionize your unit tests.
-
How to improve third-party libraries with Kotlin extensions
The extensions are not particularly useful in this scenario because the described functionality can be incorporated into the Host class. On the other hand, they flourish in test frameworks like Kotest and enable the rapid development of useful add-ons like custom matchers. Extending third-party libraries with utility functions is another prevalent use case. In the next sections, we'll zero in on this specific aspect.
- Are there any plans to make a better build system for Kotlin than Gradle?
-
Testing with fakes different states?
We're using Kotest for our unit tests and are quite happy with it.
-
Testing with Kotlin and JUnit5
Basic testing in Kotlin with Kotest built for kotlin specificatlly (upcoming)
-
Kotlin&Junit vs Groovy&Spock
Here you are: https://github.com/kotest/kotest/issues/189
What are some alternatives?
c3p0 - a mature, highly concurrent JDBC Connection pooling library, with support for caching and reuse of PreparedStatements.
spek - A specification framework for Kotlin
spring-boot-r2dbc - An example implementation of Spring Boot R2DBC REST API with PostgreSQL database.
mockk - mocking library for Kotlin
Vibur DBCP - Vibur DBCP - concurrent and dynamic JDBC connection pool
Kluent - Fluent Assertion-Library for Kotlin
JDBI - The Jdbi library provides convenient, idiomatic access to relational databases in Java and other JVM technologies such as Kotlin, Clojure or Scala.
strikt - An assertion library for Kotlin
Flyway - Flyway by Redgate • Database Migrations Made Easy.
hamkrest - Hamcrest for Kotlin
jOOQ - jOOQ is the best way to write SQL in Java
mockito-kotlin - Using Mockito with Kotlin