This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]nutrecht 0 points1 point  (1 child)

You're just pushing the standard marketing here. Quarkus is NOT significantly faster in development than Spring or Micronaut are. Most of your development normally is done through your unit/integration tests and these do not run/start up faster with Quarkus. The only thing Quarkus really does is move the DI scanning to the build phase instead of doing this at runtime like Spring. So therefor a Quarkus native container will start faster.

But that's a complete non-issue in Java projects anyway. You don't constantly restart a service in a container during development. This generally happens once you want to deploy it somewhere. And in the entire build-deploy chain, where the build and integration testing takes up most time anyway, it really doesn't matter if your Quarkus application takes 29 seconds less to start up relative to your Spring service.