Skip to content

Commit badaf45

Browse files
committed
Add a bit more guidance on handling work after dev service startup
1 parent b904bea commit badaf45

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

_posts/2026-01-05-new-dev-services-api.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -204,6 +204,8 @@ This isn’t possible, because a dev service would never be started in the build
204204
To pass configuration to the application, you can
205205
https://quarkus.io/guides/writing-extensions#injecting-configuration-into-recorders[use recorders].
206206

207+
In general, the Quarkus philosophy is to move work from application start to build-time, not the other way round. If you do need to move work into a `postStartHook` or recorder, try to move as little as possible, to avoid negative performance impacts. Often, code needs to know that a Dev Service *will* be created, but not the actual address. This can be handled as part of the normal build flow using a marker build item, leaving the bare minimum to execute as part of the hook.
208+
207209
==== How can I publish links to my service in the Dev UI?
208210

209211
If your service has an admin console, it's a nice pattern to publish a link to it in the Dev UI.

0 commit comments

Comments
 (0)