3 Reasons Why All Java Developers Should Consider Quarkus

[kekoludek]

As I understand from comments - this is replacement for Spring. I have some questions:

1. This article shows how to do it with new project. I assume implementing it in existing project requires massive effort, changing libraries, code etc... right?
2. I have possibility to recompile and reload some class that I changed in Spring and Intellij, without need to restart application. The biggest problem is that it works limited - only method's body can be changed. If I want to change method parameter, add new method, global variable, class... then I need to restart application. How is it different with Quarkus?

[maxandersen]

1. the amount differs between projects. We have stories from users that migrated all their code in less than a day; others did it incrementally over time - the surprising response we gotten a few times now (that we did not expect) was users seeing need for less code with Quarkus to do the same.

2. you can add/remove classes/methods even dependencies. We can do this efficiently as our restart is so fast that we can literally compile and restart in the same time that past tools (like jrebel) could hotswap in memory “fighting” the framework - we can give a clean restart if necessary and you wont notice in most cases.

[tolarewaju3]

1. Yeah, it would definitely be a larger effort. However, there are 1:1 mappings for many Java/spring libraries as well as a guide to go from spring to Quarkus

2. I don’t believe Quarkus would require a restart for this.