In the k8s era, it's easily possible to have several running instances of a service and load balance between them.
The problem with the current reminder system (_start_jobschedulers) is that it will be executed per instance (AKA pods for k8s), so we will have some reminders, some load on database, some web hook calls and ....
The solution can be having a separate binary, that will be executed separately with a corn service (OS or k8s).
In the k8s era, it's easily possible to have several running instances of a service and load balance between them. The problem with the current reminder system (_start_jobschedulers) is that it will be executed per instance (AKA pods for k8s), so we will have some reminders, some load on database, some web hook calls and ....
The solution can be having a separate binary, that will be executed separately with a corn service (OS or k8s).