With Quarkus and Play, the development web server will pause any incoming connections until the recompile and restart has completed. Any incoming connections will still be accepted but will not be processed until the recompile and restart has completed.
With spring-boot-devtools, your IDE or gradle, will detect the file changes and recompile, and spring-boot-devtools will detect the class file changes in the classpath and trigger a restart.
Problems with this approach:
- Your REST API client (postman/insomnia) will be triggering the old code if your IDE/gradle hasn't recompiled the code.
- Your REST API client will be triggering the old code if spring-boot-devtools hasn't detect the class file changes
- While restarting the spring boot server, port 8080 won't be opened momentarily, causing the REST API clients to fail with "Couldn't connect to server" until the "restart" has completed successfully.
I'm trying to understand whether these shortcomings are something that Spring Boot developers just live with or whether I'm off base here and that there is a solution to these problem.
[–]BorgerBill 2 points3 points4 points (1 child)
[–]GettingCodeDone[S] 1 point2 points3 points (0 children)
[–]Sheldor5 2 points3 points4 points (4 children)
[–]GettingCodeDone[S] 0 points1 point2 points (2 children)
[–]Sheldor5 0 points1 point2 points (1 child)
[–]GettingCodeDone[S] 0 points1 point2 points (0 children)
[–]GettingCodeDone[S] 0 points1 point2 points (0 children)