Simplicity
JDBI provides a simple, fluent API that makes accessing relational databases in Java more streamlined and less error-prone than using plain JDBC.
SQL-centric Approach
JDBI allows developers to work directly with SQL, offering the flexibility to use any SQL feature without abstraction limitations.
Ease of Integration
JDBI is easy to integrate into existing projects and works seamlessly with various database systems.
Declarative Mapping
It supports declarative and annotation-based data mapping, reducing boilerplate code when converting between database rows and Java objects.
Extensibility
JDBI's plugin architecture allows developers to extend its capabilities easily with custom features or integrate with other libraries.
We have collected here some useful links to help you find out if JDBI is good.
Check the traffic stats of JDBI on SimilarWeb. The key metrics to look for are: monthly visits, average visit duration, pages per visit, and traffic by country. Moreoever, check the traffic sources. For example "Direct" traffic is a good sign.
Check the "Domain Rating" of JDBI on Ahrefs. The domain rating is a measure of the strength of a website's backlink profile on a scale from 0 to 100. It shows the strength of JDBI's backlink profile compared to the other websites. In most cases a domain rating of 60+ is considered good and 70+ is considered very good.
Check the "Domain Authority" of JDBI on MOZ. A website's domain authority (DA) is a search engine ranking score that predicts how well a website will rank on search engine result pages (SERPs). It is based on a 100-point logarithmic scale, with higher scores corresponding to a greater likelihood of ranking. This is another useful metric to check if a website is good.
The latest comments about JDBI on Reddit. This can help you find out how popualr the product is and what people think about it.
Directly using the JDBC API in your application code is low-level and verbose. That's why libraries like Jdbi, Spring JDBC Template And Sql2o exist. They provide: named parameters, row mapping, pluggable data type binders/ row mappers/ JSON mappers. - Source: dev.to / 4 months ago
Suppose we're developing an application that allows speakers to submit their talks to a conference (for simplicity, we'll only record the talk's title). Following the Transaction Script pattern, the method for submitting a talk might look like this (using JDBI for SQL):. - Source: dev.to / over 1 year ago
_relational_ is the key word you're missing. ORMs map _objects_ to _relations_ (i.e. tables). "Unlike ORM frameworks, MyBatis does not map Java objects to database tables but Java methods to SQL statements." https://en.wikipedia.org/wiki/MyBatis "Jdbi is not an ORM. It is a convenience library to make Java database operations simpler and more pleasant to program than raw JDBC." https://jdbi.org/ "While jOOQ is not... - Source: Hacker News / over 1 year ago
While this may work for greenfield applications, I don't see this working well for preexisting schemas. From their getting started page: "Database fields are automatically created for any abstract getter methods", which definitely scares me away since they seem to be relying on automatic field type conversions. I prefer to manage my schemas when I can and do type and DAO conversions via mapper classes in the very... - Source: Hacker News / almost 3 years ago
Someone else mentioned jOOQ, but personally I also rather enjoyed JDBI3: https://jdbi.org/#_introduction_to_jdbi_3 It addresses the issues with using JDBC directly (not nice ergonomics), while still letting you work with SQL directly without too many abstractions in the middle. In combination with Dropwizard, it was pretty pleasant: https://www.dropwizard.io/en/stable/manual/jdbi3.html Other than that, I actually... - Source: Hacker News / almost 3 years ago
> I've been doing ORM on Java since Hibernate was new, and it has always sucked. Have you ever looked at something like myBatis? In particular, the XML mappers: https://mybatis.org/mybatis-3/dynamic-sql.html Looking back, I actually quite liked it - you had conditionals and ability to build queries dynamically (including snippets, doing loops etc.), while still writing mostly SQL with a bit of XML DSL around it,... - Source: Hacker News / about 3 years ago
I found JDBi[1] to be a really nice balance between ORM and raw SQL. It gives me the flexibility I need but takes care of a lot of the boilerplate. It's almost like a third category. 1. http://jdbi.org. - Source: Hacker News / about 3 years ago
You could use something like jdbi or mybatis. It's not as ugly as raw jdbc and easier to use without all of the gunk from an ORM like hibernate. Source: over 3 years ago
We use JDBI. Very simple and lightweight. It uses an object mapper not a full fledged ORM. Source: over 3 years ago
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. Source: over 3 years ago
As seems that Micronaut does not include anything similar by default, we use JDBI and that SQL to retrieve one random greeting from the greetings table. - Source: dev.to / over 3 years ago
More personally, I'm not much an ORM guy. I've just never found that the benefits outweigh the costs, but that's just my opinion. That said, I don't use JDBC directly in my own projects anymore, strongly preferring to use JDBI instead. I find that it walks the line between "make using the database easier" and "get between you and the database" beautifully. But there's not a darn thing wrong with using JDBC directly. Source: almost 4 years ago
I really like JDBI. Itโs thin enough that it lets you do anything SQL can do, but opinionated enough to provide a sane, sturdy, structured approach to working with a database. Source: almost 4 years ago
JDBI - shares features/ideas with many others but is the best of breed. Source: almost 4 years ago
For data, we use S3/MinIO, sharded PostgreSQL, and Elasticsearch. For accessing the database, we don't use Java Persistence API (JPA) but JDBI.org as it is easier to tweak queries manually, and we use a lot of specific queries and offload some processing to the database. Many of them are written to use PostgreSQL's specific features, e.g., JSONB columns, so we don't consider database independence a critical factor. - Source: dev.to / about 4 years ago
Another option is JDBI, that helps you with mappings too while having less features than JPA: https://jdbi.org/. Source: about 4 years ago
Hi! Iโm not familiar with this particular exception in combination with Micronaut, because my team has chosen to use JDBI rather than Hibernate. Source: about 4 years ago
By the way, you probably don't need Spring Data and Hibernate, if you apply the Transaction Script pattern. Since all business rules are bound to services, Hibernate will bring overhead and not so many benefits. Instead, you could try to use JDBI, JOOQ or even plain JDBC. - Source: dev.to / over 4 years ago
I really like Jdbi which I feel has a very similar goal than your library. Source: over 4 years ago
There are plenty of alternatives to ORMs. We use JDBI (https://jdbi.org) which is dead simple and a happy medium between pure JDBC and a full blown ORM. Even using the built-in JDBC support is an option with modern Java, PreparedStatement and ResultSet implement AutoClosable, which means you can write code like this:- Source: Hacker News / almost 5 years agotry (.
Ideally I'd like to use something like https://jdbi.org/ - ORM which only does conversion from rows to objects, no other magic. But I don't think it exists for node. Source: about 5 years ago
Do you know an article comparing JDBI to other products?
Suggest a link to a post with product alternatives.
Is JDBI good? This is an informative page that will help you find out. Moreover, you can review and discuss JDBI here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.