{"id":22538375,"url":"https://github.com/shuttle/shuttle.esb.scheduling","last_synced_at":"2025-07-29T16:41:55.918Z","repository":{"id":10788856,"uuid":"13058326","full_name":"Shuttle/Shuttle.Esb.Scheduling","owner":"Shuttle","description":"A simple scheduling solution built on Shuttle.Esb.","archived":false,"fork":false,"pushed_at":"2024-01-16T19:35:01.000Z","size":1819,"stargazers_count":2,"open_issues_count":1,"forks_count":4,"subscribers_count":2,"default_branch":"master","last_synced_at":"2025-07-18T17:49:13.024Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":"C#","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"bsd-3-clause","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/Shuttle.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2013-09-24T08:07:19.000Z","updated_at":"2023-08-24T11:29:50.000Z","dependencies_parsed_at":"2024-11-10T16:39:20.151Z","dependency_job_id":null,"html_url":"https://github.com/Shuttle/Shuttle.Esb.Scheduling","commit_stats":{"total_commits":62,"total_committers":1,"mean_commits":62.0,"dds":0.0,"last_synced_commit":"4e909db178f2c088472891791c43867593f6236b"},"previous_names":["shuttle/shuttle-scheduling"],"tags_count":3,"template":false,"template_full_name":null,"purl":"pkg:github/Shuttle/Shuttle.Esb.Scheduling","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Shuttle%2FShuttle.Esb.Scheduling","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Shuttle%2FShuttle.Esb.Scheduling/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Shuttle%2FShuttle.Esb.Scheduling/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Shuttle%2FShuttle.Esb.Scheduling/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/Shuttle","download_url":"https://codeload.github.com/Shuttle/Shuttle.Esb.Scheduling/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Shuttle%2FShuttle.Esb.Scheduling/sbom","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":267718721,"owners_count":24133462,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-07-29T02:00:12.549Z","response_time":2574,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-12-07T11:11:47.020Z","updated_at":"2025-07-29T16:41:55.498Z","avatar_url":"https://github.com/Shuttle.png","language":"C#","readme":"# Shuttle.Esb.Scheduling\n\nA simple scheduling solution built on Shuttle.Esb.\n\nSee [Shuttle.Esb.Scheduling.Server](https://github.com/Shuttle/Shuttle.Esb.Scheduling/tree/master/Shuttle.Esb.Scheduling.Server) for an example implementation of a scheduler.\n\n## Simple Configuration\n\nA schedule has a name for your scheduled job, e.g. **ProcessAccounts**.  You then use a [cron](https://www.pendel.co.za/shuttle-core/infrastructure/shuttle-core-cron.html) expression to indicate when a `ScheduleNotification` message is published.  Any endpoint that is interested in the notification can then subscribe to the `ScheduleNotification` message and perform the relevant processing.\n \n### cron samples\n\nFormat is {minute} {hour} {day-of-month} {month} {day-of-week}\n\n```\n{minutes} : 0-59 , - * /\n{hours} : \t0-23 , - * /\n{day-of-month} 1-31 , - * ? / L W\n{month} : 1-12 or JAN-DEC\t, - * /\n{day-of-week} : 1-7 or SUN-SAT , - * ? / L #\n\nExamples:\n* * * * * - is every minute of every hour of every day of every month\n5,10-12,17/5 * * * * - minute 5, 10, 11, 12, and every 5th minute after that\n```\n\n## How does it fit together?\n\nThe basic idea behind the scheduling is that you will have endpoints that already contain the required behaviour.  For instance, you may have a `PrintInvoices` that you can send to an endpoint to perform the processing.  You periodically click on a button and this sends off the command.  However, you do not want to necessarily send the **PrintInvoices** from the scheduler as it should not be that tightly coupled to any message.\n\nInstead you can set up how often a named `ScheduleNotification` is published.  In this case it may be the same endpoint that processes the `PrintInvoices` can subscribe to the `ScheduleNotification`.  It is, therefore, quite conceivable that an endpoint may receive a number of published `ScheduleNotification` messages, each with a different `Name`.  The handler for this command on the endpoint could use a `switch` statement to then do a `bus.Send` to send the relevant ***actual*** command to be processed, typically by configuring the message to be sent locally.\n\nBy adding this layer of indirection we can have enterprise-grade scheduling that is not at all intrusive and leverages existing functionality.\n","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fshuttle%2Fshuttle.esb.scheduling","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fshuttle%2Fshuttle.esb.scheduling","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fshuttle%2Fshuttle.esb.scheduling/lists"}