Thanks and I will definitely add that to article, I will just point to major shortcomings here of quartz (the go to job scheduler) scaling beyond one node is d

Thanks and I will definitely add that to article, I will just point to major shortcomings here of quartz (the go to job scheduler) scaling beyond one node is difficult because * as it uses db locks to adding more nodes does not scale linearly. * we can add custom partitioning (consistent hashing) on top of multi node multi db setup, but maintaining such setup would be very difficult eg adding and removing nodes, handling node failure (will have to move data around from its db to let other node execute those schedules).