6 ms·

I am currently using it for a pesonal project and so far it's been great. Expect from a few quirks here and there with new integrations and the fact that I hat

I am currently using it for a pesonal project and so far it's been great. Expect from a few quirks here and there with new integrations and the fact that I hate hibernate and there is no other option for persistance, it's great. Super fast reload, easy to implement, good developer tools.

happyweasel 6y ago
What are the advantages to ... let's say ... Spring Boot?
- barrkel 6y ago
  Better integration with k8s, mainly through more opinionated libraries (you're less likely to accidentally choose heavyweight thing which tend your service towards monolith), faster startup & faster reloads during development. https://github.com/spring-projects/spring-framework/issues/20906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel https://github.com/spring-projects/spring-framework/issues/2... is an open issue for Spring; the moral equivalent is closed for Quarkus. If you have DI misconfiguration, you tend to get it at build time rather than runtime.
- soco 6y ago
  The equivalent would be actually Spring GraalVM Native. Not bad either but somehow for me it didn't work, so I started with Quarkus and didn't look back.
- acg62 6y ago
  Just about to put a substantial project into production using Quarkus. I would say the main advantages vs SB are: * mostly uses standard javax/Jakarta/Eclipse etc APIs so code is relatively portable (in ~600 classes I found 8 quarkus imports) * build time DI/weaving * best dev-mode autoreloading I have seen * in general, less Spring-y * less reliance on classpath-searching and reflection voodoo, less weird shit breaking bc of dependency version conflicts * stack traces and class names (https://gist.github.com/thom-nic/2c74ed4075569da0f80b https://gist.github.com/thom-nic/2c74ed4075569da0f80b) that fit within a human’s field of vision * less overriding feeling of death by OOP We started with Spring Boot, switched about halfway through and never looked back.
  - pjmlp 6y ago
    > mostly uses standard javax/Jakarta/Eclipse etc APIs This is the selling point for me, never was a Spring fan.
davnicwil 6y ago
A little bit of a tangent but just out of curiosity, what would be your preferred option for persistence?
- vips7L 6y ago
  JPA is just starting to show it's years. The standard hasn't kept up. For me personally, I'd like to see something like EntityFramework, but in Java. No annotation hell, linq queries are amazing too. I know a lot of people are moving to just using jOOQ as well.
  - thom 6y ago
    This is interesting to me because on the whole I feel like I was doing way more interesting things in Hibernate 15 years ago than I see people doing with ORMs today (batching, dictionaries with entity keys, custom type serializers etc). Linq is lovely of course but I’m intrigued to hear what other ways you feel the industry has moved on in this area.
    - vips7L 6y ago
      Upserting, typesafe queries instead of raw strings, disconnecting my domain model from jpa, disconnecting my domain model from validation etc. It's also really difficult to use an EntityManager outside of a JEE/Spring/framework container. They're not thread safe and you have to manage their lifetimes manually.
- gwittel 6y ago
  Not the OP, but I generally prefer JDBI for persistence in Java. Much less random glue/boilerplate vs Hibernate. It doesn't seem to have an official Quarkus integration, but you can just pull it in like any other dependency.
  - cmckn 6y ago
    Same, I just write my own SQL and row mappers. It's not a huge deal, and then I actually know what the schema looks like (and why queries are slow ;). Hibernate has way too much magic going on under the covers. I have loved Dropwizard in the past, which encourages the use of Liquibase. Not right for every project, but it was great when it fit.

happyweasel 6y ago

What are the advantages to ... let's say ... Spring Boot?

barrkel 6y ago
Better integration with k8s, mainly through more opinionated libraries (you're less likely to accidentally choose heavyweight thing which tend your service towards monolith), faster startup & faster reloads during development. https://github.com/spring-projects/spring-framework/issues/20906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel https://github.com/spring-projects/spring-framework/issues/2... is an open issue for Spring; the moral equivalent is closed for Quarkus. If you have DI misconfiguration, you tend to get it at build time rather than runtime.
soco 6y ago
The equivalent would be actually Spring GraalVM Native. Not bad either but somehow for me it didn't work, so I started with Quarkus and didn't look back.
acg62 6y ago
Just about to put a substantial project into production using Quarkus. I would say the main advantages vs SB are: * mostly uses standard javax/Jakarta/Eclipse etc APIs so code is relatively portable (in ~600 classes I found 8 quarkus imports) * build time DI/weaving * best dev-mode autoreloading I have seen * in general, less Spring-y * less reliance on classpath-searching and reflection voodoo, less weird shit breaking bc of dependency version conflicts * stack traces and class names (https://gist.github.com/thom-nic/2c74ed4075569da0f80b https://gist.github.com/thom-nic/2c74ed4075569da0f80b) that fit within a human’s field of vision * less overriding feeling of death by OOP We started with Spring Boot, switched about halfway through and never looked back.
- pjmlp 6y ago
  > mostly uses standard javax/Jakarta/Eclipse etc APIs This is the selling point for me, never was a Spring fan.

davnicwil 6y ago

A little bit of a tangent but just out of curiosity, what would be your preferred option for persistence?

vips7L 6y ago
JPA is just starting to show it's years. The standard hasn't kept up. For me personally, I'd like to see something like EntityFramework, but in Java. No annotation hell, linq queries are amazing too. I know a lot of people are moving to just using jOOQ as well.
- thom 6y ago
  This is interesting to me because on the whole I feel like I was doing way more interesting things in Hibernate 15 years ago than I see people doing with ORMs today (batching, dictionaries with entity keys, custom type serializers etc). Linq is lovely of course but I’m intrigued to hear what other ways you feel the industry has moved on in this area.
  - vips7L 6y ago
    Upserting, typesafe queries instead of raw strings, disconnecting my domain model from jpa, disconnecting my domain model from validation etc. It's also really difficult to use an EntityManager outside of a JEE/Spring/framework container. They're not thread safe and you have to manage their lifetimes manually.
gwittel 6y ago
Not the OP, but I generally prefer JDBI for persistence in Java. Much less random glue/boilerplate vs Hibernate. It doesn't seem to have an official Quarkus integration, but you can just pull it in like any other dependency.
- cmckn 6y ago
  Same, I just write my own SQL and row mappers. It's not a huge deal, and then I actually know what the schema looks like (and why queries are slow ;). Hibernate has way too much magic going on under the covers. I have loved Dropwizard in the past, which encourages the use of Liquibase. Not right for every project, but it was great when it fit.