The scheduler needs to take instructions like "run service X every day at 6:15 with parameters Y", and ensure that the run actually happens. Modifying scheduled runs also needs to be possible. The scheduler should also probably be stateless, in the sense that all information about what is scheduled should be stored in the database, and one should be able to nuke the backend web server and start a new one, and it should read the current schedules from the database and continue functioning seamlessly.
Unsure how this would best be implemented. Some cron-like thing running as part of, or in parallel to, the FastAPI backend app is the likely solution. The first thing to do would be google around for standard ways and tools for handling this.
The scheduler needs to take instructions like "run service X every day at 6:15 with parameters Y", and ensure that the run actually happens. Modifying scheduled runs also needs to be possible. The scheduler should also probably be stateless, in the sense that all information about what is scheduled should be stored in the database, and one should be able to nuke the backend web server and start a new one, and it should read the current schedules from the database and continue functioning seamlessly.
Unsure how this would best be implemented. Some cron-like thing running as part of, or in parallel to, the FastAPI backend app is the likely solution. The first thing to do would be google around for standard ways and tools for handling this.