Hi Jasvinder, we are using scheduler to perform health checks on external api - 1) is this a good idea to use scheduler to check if any website is up ? How long it is going to run then ? 2) is there any way we can stop the scheduler. Because our scheduler will be running every 10 secs Please answer. Thanks
Hi, proactively checking the health of an external service using a scheduler is a good practice. In Spring, you can stop schedulers programmatically at runtime if needed. For more details, you can refer to the official Spring scheduler documentation.
@@SagguUK hi ... did schedulers running in background make application slow? I think if it runs infinitely that will be very bad for your application. I don't find running schedulers in background for a health check is a good idea. What is your opinion?
@@rohanyadav7327 Dear Rohan, Schedulers themselves are lightweight threads, so their impact on performance is minimal. In fact, there are always multiple schedulers running in the background, often without us even noticing. The key factor that determines performance is the business logic you've implemented within the scheduler. If that logic is efficient, the scheduler should run smoothly without any issues.
Perfect explanation!
This is a great explanation !!!
Thanks for this Saggu
Hi . My thread printing 2 times in log . What to do?
Hi Jasvinder, we are using scheduler to perform health checks on external api -
1) is this a good idea to use scheduler to check if any website is up ? How long it is going to run then ?
2) is there any way we can stop the scheduler. Because our scheduler will be running every 10 secs
Please answer. Thanks
Hi, proactively checking the health of an external service using a scheduler is a good practice. In Spring, you can stop schedulers programmatically at runtime if needed. For more details, you can refer to the official Spring scheduler documentation.
@@SagguUK hi ... did schedulers running in background make application slow? I think if it runs infinitely that will be very bad for your application. I don't find running schedulers in background for a health check is a good idea. What is your opinion?
@@rohanyadav7327 Dear Rohan, Schedulers themselves are lightweight threads, so their impact on performance is minimal. In fact, there are always multiple schedulers running in the background, often without us even noticing. The key factor that determines performance is the business logic you've implemented within the scheduler. If that logic is efficient, the scheduler should run smoothly without any issues.
Thx sir
It's pronounced "S'k'eduler" not SHEduler
In the US but It’s latter in British English :)