HikariCP

光 HikariCP・A solid, high-performance, JDBC connection pool at last. (by brettwooldridge)

Stats

Basic HikariCP repo stats
7
14,984
7.4
about 1 month ago

brettwooldridge/HikariCP is an open source project licensed under Apache License 2.0 which is an OSI approved license.

HikariCP Alternatives

Similar projects and alternatives to HikariCP based on common topics and language

  • GitHub repo Hasura

    Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.

  • GitHub repo Efficient-Pagination-SQL-PoC

    A PoC that provides better guidance on creating a more efficient pagination without using SQL OFFSET and LIMIT.

  • GitHub repo editing

  • GitHub repo Vibur DBCP

    Vibur DBCP - concurrent and dynamic JDBC connection pool

  • GitHub repo FlexyPool

    FlexyPool adds metrics and failover strategies to a given Connection Pool, allowing it to resize on demand.

  • GitHub repo Hibernate

    Hibernate's core Object/Relational Mapping functionality

  • GitHub repo jOOQ

    jOOQ is the best way to write SQL in Java

NOTE: The number of mentions on this list indicates mentions on common posts. Hence, a higher number means a better HikariCP alternative or higher similarity.

Posts

Posts where HikariCP has been mentioned. We have used some of these posts to build our list of alternatives and similar projects - the last one was on 2021-02-02.
  • How big should your connection pool be?
    news.ycombinator.com | 2021-04-30
  • 25 February 2021- Daily Chat Thread
    reddit.com/r/indonesia | 2021-02-25
  • About connection pool sizing
  • Java database connection
    reddit.com/r/javahelp | 2021-02-02
    A better option is to use a connection pool such as Hikari. Just initialize your connection pool with a fixed size and fetch connections from this pool. Whenever you are done with the connection, the connection automatically gets returned to the pool.
    reddit.com/r/javahelp | 2021-02-02
    In a more modern application we might use a connection pool library (like c3p0 or HikariCP) which also supplies us a Connection, but it's pretty much doing the same thing as what we have in the application server (pooling connections with high control over the configurability).
  • Understanding Connections and Pools
    news.ycombinator.com | 2021-01-05
    Related, about sizing DB connection (counterintuitively): https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-...
  • API pagination design by using cursors instead of offsets
    news.ycombinator.com | 2020-12-26
    If the API takes a cursor and a number of items to fetch, the idea of a "page" or how large it is exists entirely on the client. You can fetch 40 results in one query and say it corresponds to the next four "pages", if you're configured to show ten items per page

    It seems worth noting a high number of concurrent queries to the same database shard as part of the same overall page load can be very wasteful of CPU as database load increase, due to the cost of context switching. https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-... dives into that.