ChatGPT actually gave some good tips ... ✅ When to keep multiple endpoints in a single worker:
ChatGPT actually gave some good tips ...
When to keep multiple endpoints in a single worker:
• You want shared logic, like auth, middleware, routing, or common utility functions.
• You want faster cold starts (Cloudflare Workers are fast, but more workers = more potential cold starts).
• You’re trying to simplify deployment, versioning, and observability.
• Your app is a cohesive unit, like a backend API or a website.
When to split into separate workers:
• You have very different workloads (e.g., image resizing vs. data API).
• You want to enforce stricter limits or security boundaries (e.g., public vs internal APIs).
• You’re deploying to different teams or lifecycles (e.g., teams own different services).
• You hit size/dependency limits (1MB per Worker code bundle).
• You want to deploy independently and reduce blast radius of changes.
When to keep multiple endpoints in a single worker:• You want shared logic, like auth, middleware, routing, or common utility functions.
• You want faster cold starts (Cloudflare Workers are fast, but more workers = more potential cold starts).
• You’re trying to simplify deployment, versioning, and observability.
• Your app is a cohesive unit, like a backend API or a website.
When to split into separate workers:• You have very different workloads (e.g., image resizing vs. data API).
• You want to enforce stricter limits or security boundaries (e.g., public vs internal APIs).
• You’re deploying to different teams or lifecycles (e.g., teams own different services).
• You hit size/dependency limits (1MB per Worker code bundle).
• You want to deploy independently and reduce blast radius of changes.
