Quarkus

Application and Data / Languages & Frameworks / Java Tools
Avatar of Scrayos
CEO at Scrayos UG (haftungsbeschränkt)·

We use Quarkus with native compilation in GraalVM for our global REST-API "Charon", that can be used by every developer to request user, server and game-data (protected through OAuth2). Quarkus offers a reliable framework, library and stack for high-quality APIs and integrates Vert.x into its core.

GraalVM pushes the performance boundaries even further with the ability to perform ahead-of-time native compilation so we can reach an incredible small memory-footprint and fast bootup-times that we need for our microservices architecture.

READ MORE
3 upvotes·24.8K views
Avatar of undefined
Avatar of Scrayos
CEO at Scrayos UG (haftungsbeschränkt)·

As the access to our global REST-API "Charon" is bound to OAuth2, we use Keycloak inside Quarkus to authenticate and authorize users of our API. It is not possible to perform any un-authenticated requests against this API, so we wanted to make really sure that the authentication/authorization component is absolutely reliable and tested. We found those attributes within Keycloak, so we used it.

READ MORE
7 upvotes·158.4K views
Avatar of undefined
Avatar of mathieubarcikowski
Technical Leader at Odigo·
Needs advice
on
Spring Boot
and
Quarkus
at
()

Moving from a classic monolithic Java EE application on-premise to a cloud application based on microservices. What is the easier framework to learn/to move on? is Quarkus enough mature for production? Is the performance of Quarkus in production the same as the benchmarks suggest?

READ MORE
(inokoa.com)
2 upvotes·200 views
Replies (2)
Recommends
Quarkus

While I cut my teeth learning Java with Spring Boot, you are beholden to some extent to where Pivotal wants to take it. I've been bitten by their decision before to make a breaking change to an API, forcing a lot of work to bring my app back up-to-date. Quarkus, however, is based on Java/Jakarta EE, which has no single company behind it and a strong history of backwards compatibility. There is no obligation to use all the Quarkus specific elements. I build my apps as plain Java EE 8 apps with a small Quarkus runner module. Your team presumably already know Java EE so there should be no re-training required.

READ MORE
3 upvotes·19 views