shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

268
active users

#jdbc

0 posts0 participants0 posts today

This is really cool and kinda insane—running modern #Perl on the #Java Virtual Machine (#JVM).

Why? Maybe you want the flexibility of Perl scripts in your JVM-based environment (including #Kotlin and #Scala) without shelling out. More reasons here: github.com/fglock/PerlOnJava/b

Anything with #XS or #FFI C code has to be ported to Java, mind you. But @fglock has been doing just that, e.g., #DBI support via #JDBC and #JSON via fastjson2.

mastodon.social/@fglock/113034

GitHubPerlOnJava/docs/WHY_PERLONJAVA.md at master · fglock/PerlOnJavaAn implementation of the Perl programming language designed to run on the Java platform - fglock/PerlOnJava

c3p0 is a JDBC Connection pooling library I first published in 2002. It is very old-school, but i like to think it is still cool.

c3p0 v0.10.0 is the first major release — well, the first release at all — in a very long time. It now includes pluggable threading with loom support, much simplified connection testing by default, a more modern, more automated build, and many many fixes, improvements and enhancements.

github.com/swaldman/c3p0

mchange.com/projects/c3p0/

GitHubGitHub - swaldman/c3p0: a mature, highly concurrent JDBC Connection pooling library, with support for caching and reuse of PreparedStatements.a mature, highly concurrent JDBC Connection pooling library, with support for caching and reuse of PreparedStatements. - swaldman/c3p0

I struggle to find the benefits of #Spring #R2DBC. It's a full rewrite of #JDBC API using non-blocking I/O. However, typical application shouldn't open more than a handful of DB connections. So, just a few threads blocked on I/O (plus some threads queued up) shouldn't be an issue. Unless you want to be purely reactive or you are connecting to massively scalable database. But in that case, virtual threads come in handy. So what's the point? #Java #reactive

#introduction
I am an open data access (#ODBC, #JDBC, and #HTTP), integration (#DataVirtualization), and data management (#DBMS and/or #KnowledgeGraph) technologist, enthusiast, and entrepreneur.

I am passionate about open standards for #GenAI, #AI, #Identity #Authenticity, #SocialMedia (#ActivityPub & #ActivityStreams), and data de-silo-fication initiatives (e.g. #SemanticWeb, #LODCloud, #LinkedData, #RWW, and #SmallData).

I don't like any kind of silo!