Skip to content
Discussion options

You must be logged in to vote

From my point of view, scheduling feels like an orchestration concern rather than a crawling concern unless the product is intentionally becoming a persistent job runner. The crawler itself mainly needs idempotent invocation, clear job status, and a clean API boundary that an external scheduler can drive reliably.

If those primitives are strong, cron-like behavior can stay outside the core without users losing anything important.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by younissk
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants