HikariCP
Exposed
HikariCP | Exposed | |
---|---|---|
33 | 28 | |
19,424 | 7,901 | |
- | 0.9% | |
6.2 | 9.5 | |
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
Exposed
-
Drizzle is just as unready for prime-time as Prisma, what else is there?
So is it like Exposed for Kotlin which is a typesafe Kotlin DSL for building sql queries? I’ve been looking for something like this in typescript! https://github.com/JetBrains/Exposed
-
Database Testing with Testcontainers and Kotlin Exposed ORM
object TestDatabase { private val mySQLContainer: MySQLContainer = MySQLContainer("mysql:8.0.26").apply { withDatabaseName("test-db") withUsername("test-user") withPassword("test-password") start() // Start the container } init { val config = HikariConfig().apply { jdbcUrl = mySQLContainer.jdbcUrl username = mySQLContainer.username password = mySQLContainer.password driverClassName = "com.mysql.cj.jdbc.Driver" maximumPoolSize = 10 } val dataSource = HikariDataSource(config) // This doesn't connect to the database but provides a descriptor for future use // In the main app, we would do this on system start up // https://github.com/JetBrains/Exposed/wiki/Database-and-DataSource Database.connect(dataSource) // Create the schema transaction { SchemaUtils.create(Users) } } }
-
I'm creating a REST API using KTOR. What's the best ORM to go with KTOR ?
Exposed SQL is pretty good.
-
speed of a left join with millions of rows
I am using Kotlins Exposed DSL to access my postgreSQL database. I am running an SQL query which involves doing a one-to-many left join, with the first table having tens of thousands of rows and the second table having millions of rows. The database is stored locally on the machine. I would expect the returned query to be less than one thousand rows.
-
Return a nested list of child table using Kotlin Exposed Dao
I understand that `referrersOn` and `referencedOn` can be used, however in the documentations StarWars example, the child table needs to have a column indicating the parent_id row it is joined to. This does not work in my case as my child table can be associated to multiple parent_ids.
-
Replicating Jetbrains Exposed Star Wars Example in IntelliJ Scratch file
I am following this wiki to learn kotlin exposed. It contains an example of 'Referencing' using Star Wars data. I would like to create a scratch and/or console file in IntelliJ which reproduces this simple example. However When I try to run the code I get errors (see below). Is there something I am missing here?
-
How are you all handling database persistence?
Exposed by JetBrains https://github.com/JetBrains/Exposed
-
Why people don't like Java?
Alternatively there are... hybrid solutions like Kotlin's https://github.com/JetBrains/Exposed or https://jdbi.org/ that don't quite... do all the heavy lifting for querying but allow you to sorta stitch queries together manually.
-
Using PostgreSQL as an Append-only Datastore with Kotlin and Exposed
In our last episode (https://youtu.be/Uza\_dWsNMUs) we worked out how to save stock items in PostgreSQL (https://www.postgresql.org/) using the JetBrains Exposed library (https://github.com/JetBrains/Exposed). This time we refactor our existing file-based storage, extracting an interface that we can implement with files, in-memory, or with Exposed. For the database version, instead of replacing items in a table when they change, we choose to implement an append-only datastore. This keeps all the old versions of every row, using a query to select the latest versions when we want to see the current state. This has the advantage that we can rebuild the state of our system if things go wrong, and may also be faster than amending when we consider transactions. This is part 62 of an exploration of where a Test Driven Development implementation of the Gilded Rose stock control system might take us in Kotlin. You can see the whole series as a playlist https://www.youtube.com/playlist?list=PL1ssMPpyqociJNwykAOB9\_KEZVW7BW7m2 and the code on GitHub https://github.com/dmcg/gilded-rose-tdd If you like this, you’ll probably like my book Java to Kotlin, A Refactoring Guidebook (http://java-to-kotlin.dev). It's about far more than just the syntax differences between the languages - it shows how to upgrade your thinking to a more functional style. I have some free time between producing videos and working for team Gilded Rose. If you like these videos I'd like to work with you - please get in touch - [email protected]
-
Writing to db
I have used hikari and exposed to do this in the past with postgres, although other dialects are supported.
What are some alternatives?
c3p0 - a mature, highly concurrent JDBC Connection pooling library, with support for caching and reuse of PreparedStatements.
Ktorm - A lightweight ORM framework for Kotlin with strong-typed SQL DSL and sequence APIs.
spring-boot-r2dbc - An example implementation of Spring Boot R2DBC REST API with PostgreSQL database.
SQLDelight - SQLDelight - Generates typesafe Kotlin APIs from SQL
Vibur DBCP - Vibur DBCP - concurrent and dynamic JDBC connection pool
kotlin-jpa-specification-dsl - This library provides a fluent DSL for querying spring data JPA repositories using spring data Specifications (i.e. the JPA Criteria API), without boilerplate code or a generated metamodel.
JDBI - The Jdbi library provides convenient, idiomatic access to relational databases in Java and other JVM technologies such as Kotlin, Clojure or Scala.
requery - requery - modern SQL based query & persistence for Java / Kotlin / Android
Flyway - Flyway by Redgate • Database Migrations Made Easy.
kwery - Kwery is an SQL library for Kotlin
jOOQ - jOOQ is the best way to write SQL in Java
kotlin-nosql - NoSQL database query and access library for Kotlin