Micronaut
JDBI
Micronaut | JDBI | |
---|---|---|
50 | 27 | |
5,951 | 1,905 | |
0.4% | 0.5% | |
9.9 | 9.4 | |
4 days ago | 17 days ago | |
Java | Java | |
Apache License 2.0 | Apache 2.0 license |
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.
Micronaut
-
Javalin – a simple web framework for Java and Kotlin
Micronaut has a share of the space too.
https://micronaut.io/
However, you’re right that Spring Boot has the lions share of the Java ecosystem.
-
Spark – A web micro framework for Java and Kotlin
I've used vert.x in a big project once. I don't ever want to do that again. Performance is pretty good, but the developer experience is beyond clunky.
My current favourite Java server framework is Micronaut.
Great performance and easy to develop for!
https://micronaut.io/
- Java 21 Released
-
Java consumes 38x less energy than Python
I wonder how much you'd save with Micronaut: https://micronaut.io/
> Micronaut is a software framework for the Java virtual machine platform. It is designed to avoid reflection, thus reducing memory consumption and improving start times. Features which would typically be implemented at run-time are instead pre-computed at compile time.
https://en.wikipedia.org/wiki/Micronaut_(framework)
I don't think you'd go down to 9, but something like 20-30 could be doable.
-
mlfx FXML compiler
I'd like to introduce my project. It is called mlfx. It can compile FXML ahead of time. It is basically an annotation processor, which internally uses Micronaut framework's AST abstraction and compiles fxml files directly to JVM bytecode. This decreases UI load time and also helps with native-image reflection configs. It also has some compliance tests that load compiled code and check resulting object graph against one loaded by javafx-xml. It also has some drawbacks now, but, please, read README. Now I'm successfully using it in two production projects.
-
What other programming languages/frameworks do you enjoy besides c#/dotnet?
https://micronaut.io/ https://quarkus.io/
-
Virtual Threads Arrive in JDK 21, Ushering a New Era of Concurrency
when it comes to full stack frameworks, Micronaut(https://micronaut.io/) is actually good and pleasant to work with.
-
Tech-stack for web application using Kotlin?
For the server Quarkus and Micronaut might be interesting besides Spring Boot. Quarkus is more popular and backed by RedHat (so probably here to stay).
-
Top 5 Server-Side Frameworks for Kotlin in 2022: Micronaut
🥇 Spring Boot 🥈 Quarkus 🥉 Micronaut 🏅 Ktor 🏅 http4k
-
Would love some guidance in how to get started with building web projects with Java.
Spring boot is still The King. Although I've not done more than hello world with Micronaut, it might have easier learning curve than Spring (and concepts are similar to Spring so you can carry over later to learn Spring). It could also be a useful skill in world of microservices these days.
JDBI
-
Permazen: Language-natural persistence to KV stores
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 simple and elegant JDBI framework where you write SQL annotations above your DAO methods https://jdbi.org/#_declarative_api
JDBI does wonders for wonky old schemas you've inherited, since joins etc work out of the box (just throw them in your annotations!) The annotations can also link to .SQL files for the big hairy queries.
All these "do magic" frameworks (hibernate being one of the first) work in the simple cases but then fall apart whenever you need to do anything complex/not-prescribed. I end up having to dig into the internals of the framework to see what's going wrong which negates their whole value add.
-
Is ORM still an anti-pattern?
> 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, which didn't suck as much as one might imagine. The only problem was that there was still writing some boilerplate, which I wasn't the biggest fan of.
Hibernate always felt like walking across a bridge that might collapse at any moment (one eager fetch away from killing the performance, or having some obscure issue related to the entity mappings), however I liked tooling that let you point towards your database and get a local set of entities mapped automatically, even though codegen also used to have some issues occasionally (e.g. date types).
That said, there's also projects like jOOQ which had a more code centric approach, although I recall it being slightly awkward to use in practice: https://www.jooq.org/ (and the autocomplete killed the performance in some IDEs because of all the possible method signatures)
More recently, when working on a Java project, I opted for JDBI3, which felt reasonably close to what you're describing, at the expense of not being able to build dynamic queries as easily, as it was with myBatis: https://jdbi.org/
That said, with the multi-line string support we have in Java now, it was rather pleasant regardless: https://blog.kronis.dev/tutorials/2-4-pidgeot-a-system-for-m...
I don't think there's a silver bullet out there, everything from lightweight ORMs, to heavy ORMs like Hibernate, or even writing pure SQL has drawbacks. You just have to make the tradeoffs that will see you being successful in your particular project.
-
Sketch of a Post-ORM
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
- Is it just me, or does the Spring Framework lead to hard-to-maintain code and confusion with annotations?
-
Can someone tell me a good resource to learn and practice JDBC in java?
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.
-
Which JVM Language Would You Choose for a New Server-Side Project?
We use JDBI. Very simple and lightweight. It uses an object mapper not a full fledged ORM.
-
Why people don't like Java?
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.
-
Top 5 Server-Side Frameworks for Kotlin in 2022: Micronaut
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.
-
Fiz um mapa interativo com os resultados do segundo turno do STE com postgres (+postgis) e openlayers
Ah! E sobre o que eu usei no backend, alem de postgres e fly.io, o backend eh eh Java, usando um framework chamado quarkus e jdbi pra fazer a interface com o banco.
-
Is JDBC becoming a “legacy” API??
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.
What are some alternatives?
Quarkus - Quarkus: Supersonic Subatomic Java.
jOOQ - jOOQ is the best way to write SQL in Java
spring-native - Spring Native is now superseded by Spring Boot 3 official native support
Spring Data JPA - Simplifies the development of creating a JPA-based data access layer.
Vert.x - Vert.x is a tool-kit for building reactive applications on the JVM
HikariCP - 光 HikariCP・A solid, high-performance, JDBC connection pool at last.
Flowable (V6) - A compact and highly efficient workflow and Business Process Management (BPM) platform for developers, system admins and business users.
sql2o - sql2o is a small library, which makes it easy to convert the result of your sql-statements into objects. No resultset hacking required. Kind of like an orm, but without the sql-generation capabilities. Supports named parameters.
Nacos - an easy-to-use dynamic service discovery, configuration and service management platform for building cloud native applications.
Querydsl - Unified Queries for Java
JaCoCo - :microscope: Java Code Coverage Library
Flyway - Flyway by Redgate • Database Migrations Made Easy.