java-keyring
HikariCP
| java-keyring | HikariCP | |
|---|---|---|
| 1 | 33 | |
| 26 | 19,424 | |
| - | - | |
| 7.2 | 6.2 | |
| 7 months ago | about 1 month ago | |
| Java | Java | |
| GNU General Public License v3.0 or later | 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.
java-keyring
-
Taking a Stand in the War on General-Purpose Computing
https://github.com/javakeyring/java-keyring
People are complaining that the OS is not able to securely identify between two applications in the same user context. So they filed a bogus CVE, where the content of the CVE is basically "Linux is not an iPhone". It is a OS app sandboxing feature request, masquerading as a bug report to the keyring team.
Read the belated reply from the gnome keyring folks, pleading with people to understand what the linux security model is, and that linux doesn't have the sandboxing capabilities that have been rolled out to other (paid) operating systems:
https://wiki.gnome.org/Projects/GnomeKeyring/SecurityPhiloso...
Yet people don't understand. They are demanding that everything be turned into an iphone (in terms of app sandboxes) but they are also demanding that once the OS vendor has the power to install a chokepoint around all the apps, that they wont set up a little toll booth there as well.
But IMO asking vendors to not exploit that for commercial gain is only going to be safeguarded by regulation. It's not going to be safeguarded by consumer choice.
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