Re:Rating 26 years of Java changes
by alex_smart on Sunday October 12, 2025 @12:19PM
(#45559338)
> you did start this with writing your own
I really did not. I only said that if you were to create your own cronService, you can reuse it by creating your library rather than copy pasting code (which is obviously insane).
> which is about as insane as writing your own database driver
No, it is not. Spring Boot’s support for async jobs and scheduled jobs is lacking. A lot of people roll their own. Including yours truly.
It is also much easier than writing a database driver so there is that.
Spring Boot’s support for async jobs and scheduled jobs is lacking.
Can you elaborate? What exactly is lacking and what version of Spring are you using?!
Re:Rating 26 years of Java changes
by alex_smart on Monday October 13, 2025 @04:40AM
(#45566166)
Compare with the functionality offered by async job systems of other full stack frameworks - eg django with celery and rails with solid-queue. It’s not even close.
I am on the latest version of Spring Boot.
I am not saying there aren't more robust scheduling libraries, people still use Quartz a lot in the Java ecosystem - was just wondering what specifically are you up against that you cannot solve with Spring's scheduling?
how do you decide whether you will write your own or pull in a dependency? this is a legit question. you did start this with writing your own “cronService” (which is about as insane as writing your own database driver) so asked about it.