myntra / goscheduler Goto Github PK

Currently, we create cron schedules and provide all the required details within them. To identify which cron is for what task, we rely either on the cron expression or on the endpoints it is calling. We aim to also include a title within the cron expression, which can aid in its identification

Currently, we are using the Uber Ringpop library for distributed peer-to-peer connections. However, as Uber has ceased active development of this library, it is necessary to find a replacement which we can used in goscheduler that is actively maintained by the community.

Currently, whenever we wish to delete a schedule, we perform a hard delete by removing the record from the database. However, completely removing the record from the database is not advisable, as we may need it for audit purposes. Therefore, we aim to implement the soft delete feature for schedules.

Since updating the payload is a common requirement, especially when users utilize schedules for performing actions (often for cron schedules), it is important to address this need. Currently, when we need to update the schedule payload, we must delete the existing cron and create a new one with the updated payload. Therefore, we aim to implement functionality that allows for updating the payload of existing cron schedules.

We allow users to update the app (making it active/inactive) and modify apps configurations. However, since there are currently no audit logs getting stored, it is challenging to determine who made what changes. Therefore, we need to implement a process to store audit logs for any actions performed on the service.