o rly? what happens if they fails? can you control the backoff period? can you schedule another job in the event it fails? what if it fails before starting the function, so your in-code error handling isn't triggered? is there a "dead-letter" queue? will the next scheduled job run if the previous run failed? should it? can you define if it should or not? can you view history of executed jobs? what if your logging function that saves that history fails? can anyone add jobs or just you/superadmin? should they? and more and more.
And these are just ones I personally ran into using GCP schedulers, pub/sub and functions.
See, what you're doing is re-inventing the wheel.
No matter how cool your tool is - there's always work in the edge cases beyond just running the job.
And these are just ones I personally ran into using GCP schedulers, pub/sub and functions.
See, what you're doing is re-inventing the wheel. No matter how cool your tool is - there's always work in the edge cases beyond just running the job.