Hello, everyone
Several months ago, I posted article in this group, I created a project called kimmer for kotlin. Now I ported it to java, called jimmer.
Project link: https://github.com/babyfish-ct/jimmer
Documentation link: https://babyfish-ct.github.io/jimmer-doc/
Due to different positioning (kimmer positioning is only the basis of my graphql upper-level solution, while jimmer positioning is to subvert the underlying development ecology of java), jimmer is far more powerful than kimmer.
I hope to have time to improve kimmer and make it as same powerful in the future.
Different between jimmer and kimmer.
-
Complete documentation
-
Object Fetcher is a very powerful feature provided by jimmer-sql, comparable to GraphQL.
Even if users do not use any GraphQL-related technology stack, they can obtain object graph query capabilities similar to GraphQL at the SQL query level.
-
Actually, kimmer support this feature, but documentation is not changed
The save command is very powerful and is one of the features that distinguish jimmer-sql from other ORMs.
If GraphQL is a powerful dynamic tree output solution, then the save command is a dynamic tree input solution.
-
Support for Spring GraphQL
Spring Boot 2.7.0 brings Spring GraphQL, and jimmer-sql provides a specialized API to speed up the development of Spring GraphQL.
-
jimmer only supports JDBC, don’t support R2DBC like kimmer did. because java does not support corotuines but project loom will be released in Java19 three months later.
submitted by /u/babyfish-ct
[link] [comments]